RFID loss-prevention based on transition risk

ABSTRACT

An RFID loss-prevention system (LPS) may monitor RFID-tagged items in a facility. An RFID reader transmits a first inventory command configured to cause tags in a first state to respond, receive a reply from a first tag, determine that the first tag has a low transition risk, and cause the first tag to switch to a second state. The reader may also receive a reply from a second tag, determine that the second tag has a high transition risk, and cause the second tag to remain in the first state. The reader may then transmit a second inventory command configured to cause tags in the first state to respond, receive a reply from the second tag in response to the second inventory command, determine that the second tag has inappropriately exited the facility, and issue an alert.

CROSS REFERENCE TO RELATED APPLICATIONS

This Application is a continuation under 35 U.S.C. § 120 of co-pendingU.S. patent application Ser. No. 15/811,554 filed on Nov. 13, 2017,which is a continuation under 35 U.S.C. § 120 of U.S. patent applicationSer. No. 15/372,458, now U.S. Pat. No. 9,818,084, filed on Dec. 8, 2016,which claim the benefit of U.S. Provisional Application Ser. No.62/265,189 filed on Dec. 9, 2015. The U.S. Patent Application and theU.S. Provisional Application are hereby incorporated by reference intheir entireties.

BACKGROUND

Radio-Frequency Identification (RFID) systems typically include RFIDreaders, also known as RFID reader/writers or RFID interrogators, andRFID tags. RFID systems can be used in many ways for locating andidentifying objects to which the tags are attached. RFID systems areuseful in product-related and service-related industries for trackingobjects being processed, inventoried, or handled. In such cases, an RFIDtag is usually attached to an individual item, or to its package.

In principle, RFID techniques entail using an RFID reader to inventoryone or more RFID tags, where inventorying involves at least singulatinga tag and receiving an identifier from the singulated tag. “Singulated”is defined as a reader singling-out one tag, potentially from amongmultiple tags, for a reader-tag dialog. “Identifier” is defined as anumber identifying the tag or the item to which the tag is attached,such as a tag identifier (TID), electronic product code (EPC), etc. Thereader transmitting a Radio-Frequency (RF) wave (alternately referred toas an “RF signal”) performs the interrogation. The RF wave is typicallyelectromagnetic, at least in the far field. The RF wave can also bepredominantly electric or magnetic in the near or transitional nearfield. The RF wave may encode one or more commands that instruct thetags to perform one or more actions.

In typical RFID systems, an RFID reader transmits a modulated RFinventory signal (an inventory command), receives a tag reply, andtransmits an RF acknowledgement signal responsive to the tag reply. Atag that senses the interrogating RF wave may respond by transmittingback another RF wave. The tag either generates the transmitted back RFwave originally, or by reflecting back a portion of the interrogating RFwave in a process known as backscatter. Backscatter may take place in anumber of ways.

The reflected-back RF wave may encode data stored in the tag, such as anumber. The response is demodulated and decoded by the reader, whichthereby identifies, counts, or otherwise interacts with the associateditem. The decoded data can denote a serial number, a price, a date, atime, a destination, an encrypted message, an electronic signature,other attribute(s), any combination of attributes, and so on.Accordingly, when a reader receives tag data it can learn about the itemthat hosts the tag and/or about the tag itself.

An RFID tag typically includes an antenna section, a radio section, apower-management section, and frequently a logical section, a memory, orboth. In some RFID tags the power-management section included an energystorage device such as a battery. RFID tags with an energy storagedevice are known as battery-assisted, semi-active, or active tags. OtherRFID tags can be powered solely by the RF signal they receive. Such RFIDtags do not include an energy storage device and are called passivetags. Of course, even passive tags typically include temporary energy-and data/flag-storage elements such as capacitors or inductors.

BRIEF SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended asan aid in determining the scope of the claimed subject matter.

RFID technology may be employed in loss-prevention systems used, forexample, by retailers. In one approach, a database maintains informationabout items in the store. Checkout readers authorize an item to leavethe store after a consumer pays for the item, and then provide thisauthorization information to the database and/or a tag associated withthe item. Point-of-exit readers read tagged items exiting the store andcheck the database and/or the tag to determine if the item is authorizedto leave.

Embodiments are directed to monitoring RFID-tagged items forunauthorized transitions from a facility. An RFID reader may transmit afirst inventory command configured to cause tags in a first state toparticipate in an inventory round, receive a first reply from a firsttag in the inventory round, determine that a first item associated withthe first tag has a low transition risk, and cause the first tag toswitch to a second state based on the low transition risk. The readermay also receive a second reply from a second tag in the first inventoryround, determine that a second item associated with the second tag has ahigh transition risk, and cause the second tag to remain in the firststate based on the high transition risk. The reader may then transmit asecond inventory command configured to cause tags in the first state toparticipate in a second inventory round, receive a third reply from thesecond tag in the second inventory round, determine that the second itemhas inappropriately exited the facility, and issue an alert.

According to some examples, a method for monitoring RFID-tagged items ina facility is provided. The method may include transmitting a firstinventory command configured to cause tags in a first state toparticipate in a first inventory round, receiving a first reply from afirst tag in the first inventory round, determining that a first itemassociated with the first tag has a low transition risk based on thefirst reply, and causing the first tag to switch to a second state basedon the low transition risk. The method may further include receiving asecond reply from a second tag in the first inventory round, determiningthat a second item associated with the second tag has a high transitionrisk based on the second reply, and causing the second tag to remain inthe first state based on the high transition risk. The method mayfurther include transmitting a second inventory command configured tocause tags in the first state to participate in a second inventoryround, receiving a third reply from the second tag in the secondinventory round, determining that the second item has inappropriatelyleft the facility based on the third reply, and issuing an alert.

According to other examples, a method for a synthesized-beamradio-frequency identification (RFID) reader (SBR) to monitorRFID-tagged items in a facility is provided. The method may includesynthesizing a first beam directed substantially into the facility,transmitting a first inventory command on the first beam configured tocause tags in a first state to participate in a first inventory round,receiving a first reply from a first tag in the first inventory round,determining that a first item associated with the first tag has a lowtransition risk based on the first reply, and causing the first tag toswitch to a second state based on the low transition risk. The methodmay further include receiving a second reply from a second tag in thefirst inventory round, determining that a second item associated withthe second tag has a high transition risk based on the second reply, andcausing the second tag to remain in the first state based on the hightransition risk. The method may further include synthesizing a secondbeam directed substantially outside the facility, transmitting a secondinventory command on the second beam configured to cause tags in thefirst state to participate in a second inventory round, receiving athird reply from the second tag in the second inventory round,determining that the second item has inappropriately left the facilitybased on the third reply, and issuing an alert.

According to further examples, a method for a radio-frequencyidentification (RFID) reader system including multiple antennas tomonitor RFID-tagged items in a facility is provided. The method mayinclude directing a first beam substantially into the facility from afirst antenna, transmitting a first inventory command on the first beamconfigured to cause tags in a first state to participate in a firstinventory round, receiving a first reply from a first tag in the firstinventory round, determining that a first item associated with the firsttag has a low transition risk based on the first reply, and causing thefirst tag to switch to a second state based on the low transition risk.The method may further include receiving a second reply from a secondtag in the first inventory round, determining that a second itemassociated with the second tag has a high transition risk based on thesecond reply, and causing the second tag to remain in the first statebased on the high transition risk. The method may further includedirecting a second beam substantially outside the facility from a secondantenna, transmitting a second inventory command on the second beamconfigured to cause tags in the first state to participate in a secondinventory round, receiving a third reply from the second tag in thesecond inventory round, determining that the second item hasinappropriately left the facility based on the third reply, and issuingan alert.

These and other features and advantages will be apparent from a readingof the following detailed description and a review of the associateddrawings. It is to be understood that both the foregoing generaldescription and the following detailed description are explanatory onlyand are not restrictive of aspects as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The following Detailed Description proceeds with reference to theaccompanying drawings, in which:

FIG. 1 is a block diagram of components of an RFID system.

FIG. 2 is a diagram showing components of a passive RFID tag, such as atag that can be used in the system of FIG. 1.

FIG. 3 is a conceptual diagram for explaining a half-duplex mode ofcommunication between the components of the RFID system of FIG. 1.

FIG. 4 is a block diagram showing a detail of an RFID tag, such as theone shown in FIG. 2.

FIGS. 5A and 5B illustrate signal paths during tag-to-reader andreader-to-tag communications in the block diagram of FIG. 4.

FIG. 6 is a block diagram showing a detail of an RFID reader system,such as the one shown in FIG. 1.

FIG. 7 is a block diagram illustrating an overall architecture of anRFID system according to embodiments.

FIG. 8 depicts an antenna array according to embodiments.

FIGS. 9A and 9B depict the antenna array of FIG. 8 synthesizing a beamin different physical directions, according to embodiments.

FIG. 10 depicts some of the potential beam locations that can besynthesized by the antenna array of FIG. 8, according to embodiments.

FIG. 11 is a diagram of a facility configured with a loss-preventionsystem (LPS).

FIG. 12 depicts how the angle-of-arrival of an RF wave can bedetermined.

FIG. 13 depicts several examples of how angle-of-arrival may be used todetermine the direction and/or velocity of a moving tag.

FIG. 14 depicts how RFID readers may be configured to provide read zonesin an environment, according to embodiments.

FIG. 15 depicts how RFID readers may be used to monitor tagged items atparticular risk of theft, according to embodiments.

FIG. 16 is a flowchart of an item-monitoring process according toembodiments.

FIG. 17 is a flowchart of a loss-prevention process according toembodiments.

DETAILED DESCRIPTION

In the following detailed description, references are made to theaccompanying drawings that form a part hereof, and in which are shown byway of illustration specific embodiments or examples. These embodimentsor examples may be combined, other aspects may be utilized, andstructural changes may be made without departing from the spirit orscope of the present disclosure. The following detailed description istherefore not to be taken in a limiting sense, and the scope of thepresent invention is defined by the appended claims and theirequivalents.

As used herein, “memory” is one of ROM, RAM, SRAM, DRAM, NVM, EEPROM,FLASH, Fuse, MRAM, FRAM, and other similar information-storagetechnologies as will be known to those skilled in the art. Some portionsof memory may be writeable and some not. “Command” refers to a readerrequest for one or more tags to perform one or more actions, andincludes one or more tag instructions preceded by a command identifieror command code that identifies the command and/or the tag instructions.“Instruction” refers to a request to a tag to perform a single explicitaction (e.g., write data into memory). “Program” refers to a request toa tag to perform a set or sequence of instructions (e.g., read a valuefrom memory and, if the read value is less than a threshold then lock amemory word). “Protocol” refers to an industry standard forcommunications between a reader and a tag (and vice versa), such as theClass-1 Generation-2 UHF RFID Protocol for Communications at 860 MHz-960MHz by GS1 EPCglobal, Inc. (“Gen2 Specification”), versions 1.2.0 and2.0 of which are hereby incorporated by reference.

FIG. 1 is a diagram of the components of a typical RFID system 100,incorporating embodiments. An RFID reader 110 transmits an interrogatingRF signal 112. RFID tag 120 in the vicinity of RFID reader 110 sensesinterrogating RF signal 112 and generate signal 126 in response. RFIDreader 110 senses and interprets signal 126. The signals 112 and 126 mayinclude RF waves and/or non-propagating RF signals (e.g., reactivenear-field signals).

Reader 110 and tag 120 communicate via signals 112 and 126. Whencommunicating, each encodes, modulates, and transmits data to the other,and each receives, demodulates, and decodes data from the other. Thedata can be modulated onto, and demodulated from, RF waveforms. The RFwaveforms are typically in a suitable range of frequencies, such asthose near 900 MHz, 13.56 MHz, and so on.

The communication between reader and tag uses symbols, also called RFIDsymbols. A symbol can be a delimiter, a calibration value, and so on.Symbols can be implemented for exchanging binary data, such as “0” and“1”, if that is desired. When symbols are processed by reader 110 andtag 120 they can be treated as values, numbers, and so on.

Tag 120 can be a passive tag, or an active or battery-assisted tag(i.e., a tag having its own power source). When tag 120 is a passivetag, it is powered from signal 112.

FIG. 2 is a diagram of an RFID tag 220, which may function as tag 120 ofFIG. 1. Tag 220 is drawn as a passive tag, meaning it does not have itsown power source. Much of what is described in this document, however,applies also to active and battery-assisted tags.

Tag 220 is typically (although not necessarily) formed on asubstantially planar inlay 222, which can be made in many ways known inthe art. Tag 220 includes a circuit which may be implemented as an IC224. In some embodiments IC 224 is implemented in complementarymetal-oxide semiconductor (CMOS) technology. In other embodiments IC 224may be implemented in other technologies such as bipolar junctiontransistor (BJT) technology, metal-semiconductor field-effect transistor(MESFET) technology, and others as will be well known to those skilledin the art. IC 224 is arranged on inlay 222.

Tag 220 also includes an antenna for exchanging wireless signals withits environment. The antenna is often flat and attached to inlay 222. IC224 is electrically coupled to the antenna via suitable IC contacts (notshown in FIG. 2). The term “electrically coupled” as used herein maymean a direct electrical connection, or it may mean a connection thatincludes one or more intervening circuit blocks, elements, or devices.The “electrical” part of the term “electrically coupled” as used in thisdocument shall mean a coupling that is one or more of ohmic/galvanic,capacitive, and/or inductive. Similarly, the term “electricallyisolated” as used herein means that electrical coupling of one or moretypes (e.g., galvanic, capacitive, and/or inductive) is not present, atleast to the extent possible. For example, elements that areelectrically isolated from each other are galvanically isolated fromeach other, capacitively isolated from each other, and/or inductivelyisolated from each other. Of course, electrically isolated componentswill generally have some unavoidable stray capacitive or inductivecoupling between them, but the intent of the isolation is to minimizethis stray coupling to a negligible level when compared with anelectrically coupled path.

IC 224 is shown with a single antenna port, comprising two IC contactselectrically coupled to two antenna segments 226 and 228 which are shownhere forming a dipole. Many other embodiments are possible using anynumber of ports, contacts, antennas, and/or antenna segments.

Diagram 250 depicts top and side views of tag 252, formed using a strap.Tag 252 differs from tag 220 in that it includes a substantially planarstrap substrate 254 having strap contacts 256 and 258. IC 224 is mountedon strap substrate 254 such that the IC contacts on IC 224 electricallycouple to strap contacts 256 and 258 via suitable connections (notshown). Strap substrate 254 is then placed on inlay 222 such that strapcontacts 256 and 258 electrically couple to antenna segments 226 and228. Strap substrate 254 may be affixed to inlay 222 via pressing, aninterface layer, one or more adhesives, or any other suitable means.

Diagram 260 depicts a side view of an alternative way to place strapsubstrate 254 onto inlay 222. Instead of strap substrate 254's surface,including strap contacts 256/258, facing the surface of inlay 222, strapsubstrate 254 is placed with its strap contacts 256/258 facing away fromthe surface of inlay 222. Strap contacts 256/258 can then be eithercapacitively coupled to antenna segments 226/228 through strap substrate254, or conductively coupled using a through-via which may be formed bycrimping strap contacts 256/258 to antenna segments 226/228. In someembodiments the positions of strap substrate 254 and inlay 222 may bereversed, with strap substrate 254 mounted beneath inlay 222 and strapcontacts 256/258 electrically coupled to antenna segments 226/228through inlay 222. Of course, in yet other embodiments strap contacts256/258 may electrically couple to antenna segments 226/228 through bothinlay 222 and strap substrate 254.

In operation, the antenna receives a signal and communicates it to IC224, which may both harvest power and respond if appropriate, based onthe incoming signal and the IC's internal state. If IC 224 usesbackscatter modulation then it responds by modulating the antenna'sreflectance, which generates response signal 126 from signal 112transmitted by the reader. Electrically coupling and uncoupling the ICcontacts of IC 224 can modulate the antenna's reflectance, as canvarying the admittance of a shunt-connected circuit element which iscoupled to the IC contacts. Varying the impedance of a series-connectedcircuit element is another means of modulating the antenna'sreflectance. If IC 224 is capable of transmitting signals (e.g., has itsown power source, is coupled to an external power source, and/or is ableto harvest sufficient power to transmit signals), then IC 224 mayrespond by transmitting response signal 126.

In the embodiments of FIG. 2, antenna segments 226 and 228 are separatefrom IC 224. In other embodiments the antenna segments may alternativelybe formed on IC 224. Tag antennas according to embodiments may bedesigned in any form and are not limited to dipoles. For example, thetag antenna may be a patch, a slot, a loop, a coil, a horn, a spiral, amonopole, microstrip, stripline, or any other suitable antenna.

An RFID tag such as tag 220 is often attached to or associated with anindividual item or the item packaging. An RFID tag may be fabricated andthen attached to the item or packaging, or may be partly fabricatedbefore attachment to the item or packaging and then completelyfabricated upon attachment to the item or packaging. In someembodiments, the manufacturing process of the item or packaging mayinclude the fabrication of an RFID tag. In these embodiments, theresulting RFID tag may be integrated into the item or packaging, andportions of the item or packaging may serve as tag components. Forexample, conductive item or packaging portions may serve as tag antennasegments or contacts. Nonconductive item or packaging portions may serveas tag substrates or inlays. If the item or packaging includesintegrated circuits or other circuitry, some portion of the circuitrymay be configured to operate as part or all of an RFID tag IC.

The components of the RFID system of FIG. 1 may communicate with eachother in any number of modes. One such mode is called full duplex, whereboth reader 110 and tag 120 can transmit at the same time. In someembodiments, RFID system 100 may be capable of full duplex communicationif tag 120 is configured to transmit signals as described above. Anothersuch mode, suitable for passive tags, is called half-duplex, and isdescribed below.

FIG. 3 is a conceptual diagram 300 for explaining half-duplexcommunications between the components of the RFID system of FIG. 1, inthis case with tag 120 implemented as passive tag 220 of FIG. 2. Theexplanation is made with reference to a TIME axis, and also to a humanmetaphor of “talking” and “listening”. The actual technicalimplementations for “talking” and “listening” are now described.

RFID reader 110 and RFID tag 120 talk and listen to each other by takingturns. As seen on axis TIME, when reader 110 talks to tag 120 thecommunication session is designated as “R→T”, and when tag 120 talks toreader 110 the communication session is designated as “T→R”. Along theTIME axis, a sample R→T communication session occurs during a timeinterval 312, and a following sample T→R communication session occursduring a time interval 326. Interval 312 may typically be of a differentduration than interval 326—here the durations are shown approximatelyequal only for purposes of illustration.

According to blocks 332 and 336, RFID reader 110 talks during interval312, and listens during interval 326. According to blocks 342 and 346,RFID tag 120 listens while reader 110 talks (during interval 312), andtalks while reader 110 listens (during interval 326).

In terms of actual behavior, during interval 312 reader 110 talks to tag120 as follows. According to block 352, reader 110 transmits signal 112,which was first described in FIG. 1. At the same time, according toblock 362, tag 120 receives signal 112 and processes it to extract dataand so on. Meanwhile, according to block 372, tag 120 does notbackscatter with its antenna, and according to block 382, reader 110 hasno signal to receive from tag 120.

During interval 326, tag 120 talks to reader 110 as follows. Accordingto block 356, reader 110 transmits a Continuous Wave (CW) signal, whichcan be thought of as a carrier that typically encodes no information.This CW signal serves both to transfer energy to tag 120 for its owninternal power needs, and also as a carrier that tag 120 can modulatewith its backscatter. Indeed, during interval 326, according to block366, tag 120 does not receive a signal for processing. Instead,according to block 376, tag 120 modulates the CW emitted according toblock 356 so as to generate backscatter signal 126. Concurrently,according to block 386, reader 110 receives backscatter signal 126 andprocesses it.

FIG. 4 is a block diagram showing a detail of an RFID IC, such as IC 224in FIG. 2. Electrical circuit 424 in FIG. 4 may be formed in an IC of anRFID tag, such as tag 220 of FIG. 2. Circuit 424 has a number of maincomponents that are described in this document. Circuit 424 may have anumber of additional components from what is shown and described, ordifferent components, depending on the exact implementation.

Circuit 424 shows two IC contacts 432, 433, suitable for coupling toantenna segments such as antenna segments 226/228 of RFID tag 220 ofFIG. 2. When two IC contacts form the signal input from and signalreturn to an antenna they are often referred-to as an antenna port. ICcontacts 432, 433 may be made in any suitable way, such as from metallicpads and so on. In some embodiments circuit 424 uses more than two ICcontacts, especially when tag 220 has more than one antenna port and/ormore than one antenna.

Circuit 424 includes signal-routing section 435 which may include signalwiring, signal-routing busses, receive/transmit switches, and so on thatcan route a signal to the components of circuit 424. In some embodimentsIC contacts 432/433 couple galvanically and/or inductively tosignal-routing section 435. In other embodiments (such as is shown inFIG. 4) circuit 424 includes optional capacitors 436 and/or 438 which,if present, capacitively couple IC contacts 432/433 to signal-routingsection 435. This capacitive coupling causes IC contacts 432/433 to begalvanically decoupled from signal-routing section 435 and other circuitcomponents.

Capacitive coupling (and resultant galvanic decoupling) between ICcontacts 432 and/or 433 and components of circuit 424 is desirable incertain situations. For example, in some RFID tag embodiments ICcontacts 432 and 433 may galvanically connect to terminals of a tuningloop on the tag. In this situation, capacitors 436 and/or 438galvanically decouple IC contact 432 from IC contact 433, therebypreventing the formation of a short circuit between the IC contactsthrough the tuning loop.

Capacitors 436/438 may be implemented within circuit 424 and/or partlyor completely external to circuit 424. For example, a dielectric orinsulating layer on the surface of the IC containing circuit 424 mayserve as the dielectric in capacitor 436 and/or capacitor 438. Asanother example, a dielectric or insulating layer on the surface of atag substrate (e.g., inlay 222 or strap substrate 254) may serve as thedielectric in capacitors 436/438. Metallic or conductive layerspositioned on both sides of the dielectric layer (i.e., between thedielectric layer and the IC and between the dielectric layer and the tagsubstrate) may then serve as terminals of the capacitors 436/438. Theconductive layers may include IC contacts (e.g., IC contacts 432/433),antenna segments (e.g., antenna segments 226/228), or any other suitableconductive layers.

Circuit 424 also includes a rectifier and PMU (Power Management Unit)441 that harvests energy from the RF signal received by antenna segments226/228 to power the circuits of IC 424 during either or bothreader-to-tag (R→T) and tag-to-reader (T→R) sessions. Rectifier and PMU441 may be implemented in any way known in the art.

Circuit 424 additionally includes a demodulator 442 that demodulates theRF signal received via IC contacts 432, 433. Demodulator 442 may beimplemented in any way known in the art, for example including a slicer,an amplifier, and so on.

Circuit 424 further includes a processing block 444 that receives theoutput from demodulator 442 and performs operations such as commanddecoding, memory interfacing, and so on. In addition, processing block444 may generate an output signal for transmission. Processing block 444may be implemented in any way known in the art, for example bycombinations of one or more of a processor, memory, decoder, encoder,and so on.

Circuit 424 additionally includes a modulator 446 that modulates anoutput signal generated by processing block 444. The modulated signal istransmitted by driving IC contacts 432, 433, and therefore driving theload presented by the coupled antenna segment or segments. Modulator 446may be implemented in any way known in the art, for example including aswitch, driver, amplifier, and so on.

In one embodiment, demodulator 442 and modulator 446 may be combined ina single transceiver circuit. In another embodiment modulator 446 maymodulate a signal using backscatter. In another embodiment modulator 446may include an active transmitter. In yet other embodiments demodulator442 and modulator 446 may be part of processing block 444.

Circuit 424 additionally includes a memory 450 to store data 452. Atleast a portion of memory 450 is preferably implemented as a NonvolatileMemory (NVM), which means that data 452 is retained even when circuit424 does not have power, as is frequently the case for a passive RFIDtag.

In some embodiments, particularly in those with more than one antennaport, circuit 424 may contain multiple demodulators, rectifiers, PMUs,modulators, processing blocks, and/or memories.

In terms of processing a signal, circuit 424 operates differently duringa R→T session and a T→R session. The different operations are describedbelow, in this case with circuit 424 representing an IC of an RFID tag.

FIG. 5A shows version 524-A of components of circuit 424 of FIG. 4,further modified to emphasize a signal operation during a R→T sessionduring time interval 312 of FIG. 3. Demodulator 442 demodulates an RFsignal received from IC contacts 432, 433. The demodulated signal isprovided to processing block 444 as C_IN. In one embodiment, C_IN mayinclude a received stream of symbols.

Version 524-A shows as relatively obscured those components that do notplay a part in processing a signal during a R→T session. Rectifier andPMU 441 may be active, such as for converting RF power. Modulator 446generally does not transmit during a R→T session, and typically does notinteract with the received RF signal significantly, either becauseswitching action in section 435 of FIG. 4 decouples modulator 446 fromthe RF signal, or by designing modulator 446 to have a suitableimpedance, and so on.

Although modulator 446 is typically inactive during a R→T session, itneed not be so. For example, during a R→T session modulator 446 could beadjusting its own parameters for operation in a future session, and soon.

FIG. 5B shows version 524-B of components of circuit 424 of FIG. 4,further modified to emphasize a signal operation during a T→R sessionduring time interval 326 of FIG. 3. Processing block 444 outputs asignal C_OUT. In one embodiment, C_OUT may include a stream of symbolsfor transmission. Modulator 446 then modulates C_OUT and provides it toantenna segments such as segments 226/228 of RFID tag 220 via ICcontacts 432, 433.

Version 524-B shows as relatively obscured those components that do notplay a part in processing a signal during a T→R session. Rectifier andPMU 441 may be active, such as for converting RF power. Demodulator 442generally does not receive during a T→R session, and typically does notinteract with the transmitted RF signal significantly, either becauseswitching action in section 435 of FIG. 4 decouples demodulator 442 fromthe RF signal, or by designing demodulator 442 to have a suitableimpedance, and so on.

Although demodulator 442 is typically inactive during a T→R session, itneed not be so. For example, during a T→R session demodulator 442 couldbe adjusting its own parameters for operation in a future session, andso on.

In typical embodiments, demodulator 442 and modulator 446 are operableto demodulate and modulate signals according to a protocol, such as theGen2 Specification mentioned above. In embodiments where circuit 424includes multiple demodulators and/or modulators, each may be configuredto support different protocols or different sets of protocols. Aprotocol specifies, in part, symbol encodings, and may include a set ofmodulations, rates, timings, or any other parameter associated with datacommunications. In addition, a protocol can be a variant of a statedspecification such as the Gen2 Specification, for example includingfewer or additional commands than the stated specification calls for,and so on. In such instances, additional commands are sometimes calledcustom commands.

FIG. 6 is a block diagram of an RFID reader system 600 according toembodiments. RFID reader system 600 includes a local block 610, andoptionally remote components 670. Local block 610 and remote components670 can be implemented in any number of ways. For example, local block610 or portions of local block 610 may be implemented as a standalonedevice or as a component in another device. In some embodiments, localblock 610 or portions of local block 610 may be implemented as a mobiledevice, such as a handheld RFID reader, or as a component in a mobiledevice, such as a laptop, tablet, smartphone, wearable device, or anyother suitable mobile device. It will be recognized that RFID reader 110of FIG. 1 is the same as local block 610, if remote components 670 arenot provided. Alternately, RFID reader 110 can be implemented instead byRFID reader system 600, of which only the local block 610 is shown inFIG. 1.

In some embodiments, one or more of the blocks or components of readersystem 600 may be implemented as integrated circuits. For example, localblock 610, one or more of the components of local block 610, and/or oneor more of the remote component 670 may be implemented as integratedcircuits using CMOS technology, BJT technology, MESFET technology,and/or any other suitable implementation technology.

Local block 610 is responsible for communicating with RFID tags. Localblock 610 includes a block 651 of an antenna and a driver of the antennafor communicating with the tags. Some readers, like that shown in localblock 610, contain a single antenna and driver. Some readers containmultiple antennas and drivers and a method to switch signals among them,including sometimes using different antennas for transmitting and forreceiving. Some readers contain multiple antennas and drivers that canoperate simultaneously. In some embodiments, block 651 may be aphased-array antenna or synthesized-beam antenna (SBA), described inmore detail below, and local block 610 may be implemented in asynthesized-beam reader (SBR) configured to generate one or more beamsvia the SBA. A demodulator/decoder block 653 demodulates and decodesbackscattered waves received from the tags via antenna/driver block 651.Modulator/encoder block 654 encodes and modulates an RF wave that is tobe transmitted to the tags via antenna/driver block 651.

Local block 610 additionally includes an optional local processor 656.Local processor 656 may be implemented in any number of ways known inthe art. Such ways include, by way of examples and not of limitation,digital and/or analog processors such as microprocessors anddigital-signal processors (DSPs); controllers such as microcontrollers;software running in a machine such as a general purpose computer;programmable circuits such as Field Programmable Gate Arrays (FPGAs),Field-Programmable Analog Arrays (FPAAs), Programmable Logic Devices(PLDs), Application Specific Integrated Circuits (ASIC), any combinationof one or more of these; and so on. In some cases, some or all of thedecoding function in block 653, the encoding function in block 654, orboth, may be performed instead by local processor 656. In some caseslocal processor 656 may implement an encryption or authenticationfunction; in some cases one or more of these functions can bedistributed among other blocks such as encoding block 654, or may beentirely incorporated in another block.

Local block 610 additionally includes an optional local memory 657.Local memory 657 may be implemented in any number of ways known in theart, including, by way of example and not of limitation, any of thememory types described above as well as any combination thereof. Localmemory 657 can be implemented separately from local processor 656, or inan IC with local processor 656, with or without other components. Localmemory 657, if provided, can store programs for local processor 656 torun, if needed.

In some embodiments, local memory 657 stores data read from tags, ordata to be written to tags, such as Electronic Product Codes (EPCs), TagIdentifiers (TIDs) and other data. Local memory 657 can also includereference data that is to be compared to EPCs, instructions and/or rulesfor how to encode commands for the tags, modes for controlling antenna651, encryption/authentication algorithms, algorithms for tracking taglocation or movement, secret keys, key pairs, individual public and/orprivate keys, electronic signatures, and so on. In some of theseembodiments, local memory 657 is provided as a database.

Some components of local block 610 typically treat the data as analog,such as the antenna/driver block 651. Other components such as localmemory 657 typically treat the data as digital. At some point there is aconversion between analog and digital. Based on where this conversionoccurs, a reader may be characterized as “analog” or “digital”, but mostreaders contain a mix of analog and digital functionality.

If remote components 670 are indeed provided, they are coupled to localblock 610 via an electronic communications network 680. Network 680 canbe a Local Area Network (LAN), a Metropolitan Area Network (MAN), a WideArea Network (WAN), a network of networks such as the internet, or alocal communication link, such as a USB, PCI, and so on. Local block 610may include a local network connection 659 for communicating withcommunications network 680 or may couple to a separate device orcomponent configured to communicate with communications network 680.Communications on the network can be secure, such as if they areencrypted or physically protected, or insecure if they are not encryptedor otherwise protected.

There can be one or more remote component(s) 670. If more than one, theycan be located at the same location, or in different locations. They maycommunicate with each other and local block 610 via communicationsnetwork 680, or via other similar networks, and so on. Accordingly,remote component(s) 670 can use respective remote network connections.Only one such remote network connection 679 is shown, which is similarto local network connection 659, etc.

Remote component(s) 670 can also include a remote processor 676. Remoteprocessor 676 can be made in any way known in the art, such as wasdescribed with reference to local processor 656. Remote processor 676may also implement an encryption/authentication function and/or a taglocation/tracking function, similar to local processor 656.

Remote component(s) 670 can also include a remote memory 677. Remotememory 677 can be made in any way known in the art, such as wasdescribed with reference to local memory 657. Remote memory 677 mayinclude a local database, and a different database of a standardsorganization, such as one that can reference EPCs. Remote memory 677 mayalso contain information associated with commands, tag profiles, keys,or the like, similar to local memory 657.

One or more of the above-described elements may be combined together anddesignated as operational processing block 690. Operational processingblock 690 includes those components that are provided of the following:local processor 656, remote processor 676, local network connection 659,remote network connection 679, and by extension an applicable portion ofcommunications network 680 that links remote network connection 679 withlocal network connection 659. The portion can be dynamically changeable,etc. In addition, operational processing block 690 can receive anddecode RF waves received via antenna/driver 651, and causeantenna/driver 651 to transmit RF waves according to what it hasprocessed.

Operational processing block 690 includes either local processor 656, orremote processor 676, or both. If both are provided, remote processor676 can be made such that it operates in a way complementary with thatof local processor 656. In fact, the two can cooperate. It will beappreciated that operational processing block 690, as defined this way,is in communication with both local memory 657 and remote memory 677, ifboth are present.

Accordingly, operational processing block 690 is location independent,in that its functions can be implemented either by local processor 656,or by remote processor 676, or by a combination of both. Some of thesefunctions are preferably implemented by local processor 656, and some byremote processor 676. Operational processing block 690 accesses localmemory 657, or remote memory 677, or both for storing and/or retrievingdata.

RFID reader system 600 operates by operational processing block 690generating communications for RFID tags. These communications areultimately transmitted by antenna/driver block 651, withmodulator/encoder block 654 encoding and modulating the information onan RF wave. Then data is received from the tags via antenna/driver block651, demodulated and decoded by demodulator/decoder block 653, andprocessed by operational processing block 690.

An RFID reader system such as the reader system 600 may interact withRFID tags by selecting, inventorying, and accessing the tags. An RFIDreader may select tags by transmitting a selection command that causesspecified tags to reply. In the Gen2 Specification, selection commandsinclude the Select command and the Challenge command. After selection,or if no selection needs to be done, a reader may inventory the tagpopulation to retrieve identifiers for individual tags within thepopulation. The reader inventories individual tags using inventorycommands that cause the tag being inventoried to respond with anidentifier at an appropriate time. For example, inventory commandsinclude the Query, QueryAdjust, QueryRep, ACK, and NAK commands of theGen2 Specification, and may include any other command that causes areceiving tag to respond with an identifier and/or determine whether itshould respond with an identifier. During the inventory process, thereader may further access or interact with particular tags using accesscommands. For example, the Gen2 Specification provides commands to reador write data to a tag, adjust restrictions associated with the tag,securely communicate with the tag, or perform a number of other actions,further specified in the Gen2 Specification.

Embodiments of an RFID reader system can be implemented as hardware,software, firmware, or any combination. Such a system may be subdividedinto components or modules. Some of these components or modules can beimplemented as hardware, some as software, some as firmware, and some asa combination. An example of such a subdivision is now described,together with the RFID tag as an additional module.

FIG. 7 is a block diagram illustrating an overall architecture of anRFID system 700 according to embodiments. RFID system 700 may besubdivided into modules or components, each of which may be implementedby itself or in combination with others. In addition, some of them maybe present more than once. Other embodiments may be equivalentlysubdivided into different modules. Some aspects of FIG. 7 are parallelwith systems, modules, and components described previously.

An RFID tag 703 is considered here as a module by itself. RFID tag 703conducts a wireless communication 706 with the remainder, via the airinterface 705. Air interface 705 is really a boundary, in that signalsor data that pass through it are not intended to be transformed from onething to another. Specifications as to how readers and tags are tocommunicate with each other, for example the Gen2 Specification, alsoproperly characterize that boundary as an interface.

RFID system 700 includes one or more reader antennas 710, and an RFfront-end module 720 for interfacing with reader antenna(s) 710. Thesecan be made as described above.

RFID system 700 also includes a signal-processing module 730. In oneembodiment, signal-processing module 730 exchanges waveforms with RFfront-end module 720, such as I and Q waveform pairs.

RFID system 700 further includes a physical-driver module 740, which isalso known as a data-link module. In some embodiments physical-drivermodule 740 exchanges bits with signal-processing module 730.Physical-driver module 740 can be the stage associated with the framingof data.

RFID system 700 additionally includes a media access control module 750.In one embodiment, media access control layer module 750 exchangespackets of bits with physical driver module 740. Media access controllayer module 750 can make decisions for sharing the medium of wirelesscommunication, which in this case is the air interface.

RFID system 700 moreover includes an application-programminglibrary-module 760. This module 760 can include application programminginterfaces (APIs), other objects, etc.

All of these RFID system functionalities can be supported by one or moreprocessors. One of these processors can be considered a host processor.Such a host processor might include a host operating system (OS) and/orcentral processing unit (CPU), as in module 770. In some embodiments,the processor is not considered as a separate module, but one thatincludes some of the above-mentioned modules of RFID system 700. In someembodiments the one or more processors may perform operations associatedwith retrieving data that may include a tag public key, an electronicsignature, a tag identifier, an item identifier, and/or asigning-authority public key. In some embodiments the one or moreprocessors may verify an electronic signature, create a tag challenge,and/or verify a tag response.

User interface module 780 may be coupled toapplication-programming-library module 760, for accessing the APIs. Userinterface module 780 can be manual, automatic, or both. It can besupported by the host OS/CPU module 770 mentioned above, or by aseparate processor, etc.

It will be observed that the modules of RFID system 700 form a chain.Adjacent modules in the chain can be coupled by appropriateinstrumentalities for exchanging signals. These instrumentalitiesinclude conductors, buses, interfaces, and so on. Theseinstrumentalities can be local, e.g. to connect modules that arephysically close to each other, or over a network, for remotecommunication.

The chain is used in one direction for receiving RFID waveforms and inthe other direction for transmitting RFID waveforms. In receiving mode,reader antenna(s) 710 receives wireless waves, which are in turnprocessed successively by the various modules in the chain. Processingcan terminate in any one of the modules. In transmitting mode, waveforminitiation can be in any one of the modules. Ultimately, signals arerouted to reader antenna(s) 710 to be transmitted as wireless waves.

The architecture of RFID system 700 is presented for purposes ofexplanation, and not of limitation. Its particular, subdivision intomodules need not be followed for creating embodiments. Furthermore, thefeatures of the present disclosure can be performed either within asingle one of the modules, or by a combination of them. In someembodiments RFID system 700 can be incorporated into another electronicdevice such as a checkout terminal in a store or a consumer device suchas a mobile phone.

Everything described above in terms of readers and reader componentsfinds some correspondence with tags and tag ICs, and vice versa.Numerous details have been set forth in this description, which is to betaken as a whole, to provide a more thorough understanding of theinvention. In other instances, well-known features have not beendescribed in detail, so as to not obscure unnecessarily the invention.

In some embodiments, synthesized-beam RFID readers (SBRs) may be usedfor loss prevention. An SBR is capable of generating multiple radiofrequency (RF) beams, and may be formed by coupling one or more RFIDreaders (or distributed portions of one or more readers) to an antennaarray. FIG. 8 depicts a perspective view of an antenna array 800 withdiscrete radiating elements suitable for an SBR according toembodiments. Antenna array 800 includes an array of antenna elements 802and 804, and a ground plane 808 behind elements 802 and 804. Eachelement has a radiating direction vector 806 (only shown for oneelement) that is typically, but not necessarily, perpendicular to theground plane. An RF radiation pattern (or “beam”) for receiving ortransmitting an RF signal may be synthesized by adjusting the amplitudeand/or phase of the signals coupled from/to each antenna element 802 and804. The direction of the synthesized beam (typically represented by thedirection of the beam's primary lobe—the lobe having the highestradiated power) is controlled by these various amplitude and/or phaseadjustments. The adjustments may be analog, digital, or a mix of analogand digital. For example, during transmission, an SBR may generate theanalog signal to be transmitted, split the signal, and then direct thesplit signals to elements 802 and 804 with different amplitudes andphases. Alternatively, the SBR may synthesize different signals for eachantenna element digitally and then convert the digital signals toanalog. In other embodiments the SBR may use a mix of these approaches.Similarly, during a receive operation the SBR may combine analog signalsafter appropriate phase shifting and amplitude adjustment of each, or itmay digitize the signals from each element and combine them digitally,or a mix thereof.

The antenna elements of SBA 800 may be one or more of patch, slot, wire,horn, helical, distributed, or any other type as will be known to thoseskilled in the art. Whereas FIG. 8 only shows nine antenna elements,antenna arrays with any number of antenna elements may be used,including a single distributed element or an element made frommetamaterials. In some embodiments ground plane 808 may be nonplanar(e.g., curved, concave, convex, etc.) and in other embodiments need notexist.

FIGS. 9A and 9B show the directions of some of the RF beams that SBA900, similar to SBA 800 in FIG. 8, can generate. SBA 900 has nineantenna elements 902-918, with element 902 at the center and elements904-918 around it. The shape and direction of the beam that SBA 900generates depends on the signals to/from each element. Suppose that SBR900 transmits using primarily elements 902, 906, and 914. Then,depending on the amplitude and phase of the signals applied to theseelements, SBA 900 can steer a beam along the direction indicated bydashed line 920. In a similar fashion, suppose that SBR 900 transmitsprimarily using elements 902, 908, and 916. Then, depending on theamplitude and phase of the signals applied to these elements, SBA 900can steer a beam along the direction indicated by dashed line 922. Ofcourse, other steering arrangements are possible, including using all 9elements to transmit and/or receive in arbitrary directions and togenerate narrow beams.

FIG. 9B shows how RF beams with different directions can be synthesizedusing antenna elements located along line 920, with the diagram to theleft depicting a head-on view similar to FIG. 9A and the diagram to theright depicting a side view. As described above, the beam direction canbe controlled by varying the amplitude and phase of the signals to/fromthe antenna elements. For example, by applying a leading signal phase toelement 906, an intermediate signal phase to element 902, and a trailingsignal phase to element 914, the SBA will tend to steer its beamdownward as in beam 934. Switching leading and lagging from elements906/902 to elements 902/906 will tend to steer the beam upwards as inbeam 930. Of course, the actual beam shape depends on both the magnitudeof the phase shifting and the magnitude of the amplitude scaling (ifany).

FIG. 10 depicts potential beams from an SBR according to embodiments.Diagram 1000 depicts a side perspective of SBR 1010, capable ofsynthesizing at least five different RF beams 1012, 1013, 1014, 1015,and 1016, arranged along line 1018 (similar to line 920 in FIG. 9A),with each RF beam pointed in a different direction.

Diagrams 1020, 1040, 1060, and 1080 depict coverage areas, shown asshaded circles, of the beam patterns generated by SBR 1010. A beamgenerated by an SBR has a coverage volume, also known as the beam's“field-of-view” (FoV) or “illumination”, which is a volume inthree-dimensional space where, during transmission, the transmittedenergy density exceeds a threshold. A beam's coverage area is aprojection of the beam's illumination on a surface. The illumination andcoverage area may be different during transmit and receive, and may varywith reader or tag power, the thresholds, the distance between the SBRand the surface, and other parameters.

Diagram 1020 depicts the coverage area of central beam 1012. Diagram1040 depicts the coverage areas of the inner beams such as 1014 and1015. Diagram 1060 depicts the coverage areas of the outer beams such as1015 and 1016. Finally, diagram 1080 depicts the total coverage area ofall the beams formed by SBR 1010. As shown in diagrams 1020-1080, beamcoverage areas may overlap. For example, inner beam 1014 may overlapwith the central beam 1012, with one or more other inner beams, and withone or more other outer beams.

Whereas SBR 1010 is depicted as being able to generate and switchbetween five beams on an axis (e.g., axis 1018), in other embodiments anSBR may generate and switch between more or fewer beams on any givenaxis. Similarly, whereas SBR 1010 is depicted as being able to generatebeams on four different axes (e.g., axes 920, 922, 924, and 926 in FIG.9A), in other embodiments an SBR may be configured to generate beams onmore or fewer axes. An individual beam's coverage area in FIG. 10 andsubsequent figures is depicted as circular for simplicity, and inactuality may be of any suitable shape, and may vary based oninteractions between the different elements that form the beam, as wellas the orientation and topology of the surface on which the coveragearea is projected. For example, a beam may have a non-circular coveragearea. As another example, a circular beam that illuminates a surfacewith a non-perpendicular angle may project an elliptical coverage areaon the surface.

When used to detect and inventory RFID tags, SBR 1010 may be configuredto switch between different individual beams based on a desired beamscanning timing or pattern. For example, SBR 1010 may generate a firstbeam at a first time for a first time duration, then may switch togenerating a second, different beam at a second time for a second timeduration, and so on. The order, timing, and time durations with whichSBR 1010 switches between generating different beams may be predefinedor dynamic. In one embodiment, SBR 1010 may switch between differentbeams based on a predefined schedule and scan pattern. In anotherembodiment, SBR 1010 may dynamically determine the beams to generate,the times when they should be generated, and the time durations forwhich they should be generated based on environmental or otherconditions (e.g., the actual or estimated number of tags present, actualor predicted tag movement patterns, RF interference, environmentalnoise, or any other suitable condition or parameter). In otherembodiments, SBR 1010 may generate beams by dynamically adjusting apredefined schedule and scan pattern based on environmental conditions.SBR 1010 may be configured to switch beams to optimize the number oftags inventoried, optimize the ability to detect fast-moving tags, or beconfigured to provide any desired performance metric.

As mentioned above, RFID technology may be employed in loss-preventionsystems used to detect and prevent theft or unauthorized item movement.FIG. 11 is a diagram 1100 of a facility 1102 configured with aloss-prevention system (LPS). Facility 1102 has a perimeter or boundarydelimited by a physical or virtual wall, border, fence, or similar.Physical boundaries include a physical wall, border, fence, orentrance/exit through any of the previous. Virtual boundaries may bedetermined with respect to a physical structure (e.g., a physicalboundary such as a wall) or a location in physical space. For example, avirtual boundary may be defined as the perimeter or surface of an areaor volume extending two meters outward from a wall, or may be defined asthe perimeter/surface of an area/volume extending outward from a doorwayin the wall. Facility 1102 is depicted in FIG. 11 as a retail orwholesale store, but in other embodiments may be a building, laboratory,yard, warehouse, distribution center, construction facility, plant,military installation, transit station (e.g., a train, bus, or subwaystation or an airport), ship, parking lot, shipping container, eventgrounds (such as a fairground), portion or section of the above, alocation within or associated with one of the above, or similar.

Facility 1102 may include items tagged with RFID tags. A person, such asa customer, may remove an item having a tag 1104 from facility 1102 byfirst obtaining exit authorization from checkout station 1150, whichincludes an RFID reader. In one embodiment checkout station 1150 may bea point-of sale register or similar checkout terminal. In anotherembodiment checkout station 1150 may be a facility employee with amobile checkout device such as a handheld reader, tablet, etc. In yetanother embodiment checkout station 1150 may include or be a customermobile device such as a smartphone that has an RFID reader. Many othertypes and embodiments of checkout terminals are possible. Regardless ofthe type, checkout station 1150 reads RFID tag 1104 and can authorize itand its associated item to leave facility 1102.

Before authorizing a tagged item to leave facility 1102, checkoutstation 1150 should obtain exit authorization, typically based onauthorizing information provided by the person (e.g. customer) or anentity/proxy acting on behalf of the person. An example of the lattermay be a facility employee, a legal authority such as a security personor the police, an autonomous entity such as a monitoring/securitysystem, or any other proxy that can act on behalf of the person. Theauthorizing information may include customer identification or accountinformation, payment, payment data (e.g., electronic currency orelectronic gift card balance), payment authorization, credit-limitinformation, proof-of-payment, or other similar information. In somesituations the authorizing information may also or instead include or bean employee number, item transportation information, a security code, alegal warrant, or other information suitable for a checkout station todetermine whether tag 1104 and its associated item are authorized toleave facility 1102.

In some embodiments checkout station 1150 can self-verify theauthorizing information and generate exit authorization. In otherembodiments checkout station 1150 will engage with a linked entity toverify the authorizing information. Examples of a linked entity includea store network, store server, payment server, bank, credit-cardcompany, legal entity such as government authority, or other networkedentity. Upon verifying the authorizing information, checkout station1150 authorizes tag 1104 and its associated item to leave facility 1102.

The facility 1102 further implements a loss-prevention system (LPS)configured to detect or prevent the departure of unauthorized taggeditems from facility 1102. An LPS as described herein is configured todetermine whether a tag exiting facility 1102 is facility-owned and, ifso, whether the tag has exit authorization, for purposes of lossprevention. An LPS may include one or more tags (e.g., tag 1104), one ormore readers configured to detect tags or tagged items exiting afacility, and/or some means to determine whether a detected tag ortagged item is authorized to exit the facility. An LPS may also includeor implement security feature(s) configured to notify relevant personnelof unauthorized exits or to prevent unauthorized tags or tagged itemsfrom exiting the facility.

The LPS implemented at facility 1102 includes at least one reader 1110positioned to detect tags transitioning through exit 1120 of facility1102. Exit 1120 may include a door, doorway, gate, gateway, entryway,hallway, ramp, garage, elevator, escalator, stairway, stairwell, or anyother suitable exit or entrance. In diagram 1100, reader 1110 isdepicted as an SBR, although in some embodiments reader 1110 may includeone or more non-SBR readers (i.e., readers not configured to generatesynthesized beams) instead of or in addition to SBRs.

In diagram 1100, reader 1110 is positioned such that at least some ofthe beams it generates are directed toward or near exit 1120 of facility1102. Reader 1110 can use these particular beams, labeled as exit beams1130, to detect RFID tags (and their associated items) near,approaching, passing through, or having already passed through exit1120. Exit beams 1130 may be directed substantially at exit 1120,substantially into facility 1102 but near exit 1120, and/orsubstantially outside or out of facility 1102 but near exit 1120. Ifreader 1110 includes one or more non-SBR readers, then the non-SBRreaders may be positioned such that they generate exit beams 1130. Forexample, multiple readers may be positioned such that each readergenerates at least one of the exit beams 1130, and multiple readerantennas, which may be coupled to one or more readers, may be positionedsuch that each antenna (in combination with a coupled reader) generatesat least one of the exit beams 1130.

While reader 1110 is located within facility 1102 in FIG. 11, in otherembodiments reader 1110 may be located at exit 1120 or external tofacility 1102, as long as at least some of its beams are directed nearor toward exit 1120, e.g. to form exit beams 1130. Reader 1110 may bemounted so as to point downward (e.g., on the ceiling of facility 1102or in another elevated position), mounted so as to point horizontally(e.g., on a wall or other structure in facility 1102), mounted so as topoint upward (e.g., on, at, or under a floor or structure in facility1102), or some combination of the previous.

The LPS implemented at facility 1102 may also include database 1160.Database 1160 stores information about tagged items associated withfacility 1102. This information may include tag identifiers; itemidentifiers; physical item information such as condition, status, orlocation; chain of custody; price; tracking information; manufacturer;or any other suitable tag or item information. Database 1160 may alsostore exit authorization for tags and/or tagged items. For example, whencheckout station 1150 and/or a linked entity as described abovedetermines that tag 1104 and its associated item have exitauthorization, the checkout station 1150 and/or the linked entity mayinform database 1160 accordingly. In some embodiments database 1160 maybe prepopulated with item or tag identifiers, and exit authorization isadded to the preexisting item record. In other embodiments database 1160may not contain preexisting item or tag identifiers, in which case exitauthorization for a tag or tagged item causes database 1160 to generatea new item record for the tag or tagged item.

Database 1160 may be accessible to checkout station 1150, the linkedentity, and/or reader 1110 via a wired (e.g., Ethernet, parallel,serial, or other suitable wired protocol) or wireless (e.g., WiFi,cellular, Bluetooth, or other suitable wireless protocol) connection ornetwork. In some embodiments, database 1160 is located at facility 1102,such as on a local computer, server, or RFID reader (including reader1110 or checkout station 1150). In other embodiments database 1160 maybe located remotely and accessible via a network connection. Database1160 may reside on a single device (computer, server, or reader) or bedistributed among multiple devices.

As an illustrative but non-limiting example, suppose that a customerpurchases an item tagged with tag 1104, for example via interactionswith checkout station 1150. Checkout station 1150, upon authorizing thepurchase, may write data to tag 1104 indicating that the item associatedwith tag 1104 was properly purchased and therefore is authorized toleave facility 1102. For example, checkout station 1150 may write anelectronic signature, a ticket, and/or an exit code or sold code to tag1104 indicating that tag 1104 and its associated item are authorized toleave facility 1102. The customer then carries the tagged item throughexit 1120. Reader 1110 will send commands to and receive replies fromtag 1104 using exit beams 1130. The act of receiving replies from a tagmay be known as “reading” the tag, and the replies themselves, which mayrefer either to data sent from the tag or the RF signals sent from thetag and encoding data, may be known as “reads” of the tag. Some reads oftag 1104 will include tag 1104's item and/or tag identifier. Uponreceiving the identifier(s) the LPS may perform several actions. Theseactions may occur in series (i.e., one after the other), in parallel(i.e., two or more actions simultaneously or overlapping in time), orsome combination of the two (i.e., some actions in series and some inparallel).

A first action that the LPS may perform is to determine whether tag 1104is associated with facility 1102 (i.e., whether tag 1104 belongs to oris foreign to facility 1102). The LPS may determine the association bycomparing the tag and/or item identifier to a list of items known to beassociated with facility 1102. This item list is typically stored bydatabase 1160, but in some instances may be stored elsewhere such as ina networked location, in reader 1110, or even in tag 1104. In someembodiments, each tag associated with facility 1102 may include in itsmemory an owner code indicating that it is associated with facility 1102or an entity associated with facility 1102, and the LPS may read orretrieve the stored owner code from tags passing through exit beams1130. The LPS also knows or is able to derive the owner code, and mayread an owner code from tag 1104 and compare the read owner code withits known or derived owner code. If the two owner codes match, then theLPS may determine that tag 1104 and its associated item are associatedwith facility 1102. If the two owner codes do not match, then the LPSmay determine that tag 1104 and its associated item are not associatedwith facility 1102. As another example, the LPS may be able to derive orretrieve identifiers for tags associated with facility 1102. Uponreading an identifier from tag 1104, the LPS may compare the readidentifier to a derived/retrieved identifier to determine whether tag1104 is associated with facility 1102, where a match between the twoidentifiers indicates that tag 1104 is associated with facility 1102 anda mismatch between the two identifiers indicates that tag 1104 is notassociated with facility 1102.

A second action that the LPS may perform is to determine whether tag1104 is stationary or passing through exit 1120. It may make thisdetermination based on parameters of tag reads (e.g., RF signals sentfrom tags and encoding data) detected in exit beams 1130, such as signalphase, a received signal strength indication (RSSI), the sequence ofexit beams in which tag 1104 is read, the identity or orientation of theexit beams in which tag 1104 is read, the time at which tag 1104 wasread, and/or an angle-of-arrival of one or more RF signals received fromtag 1104. It may also, or alternatively, use or provide information suchas read count (for example, the number of reads of a tag over aparticular time duration) or read rate (for example, the rate at which atag is read as a function of time) per exit beam to determine whethertag 1104 is stationary or moving, and if the latter tag 1104's velocityand/or direction of travel. In some embodiments, tag 1104 itself may beconfigured to determine whether it is moving, and if so it may indicateits movement to the LPS, for example via a backscattered code. The LPSmay use a location-determining algorithm, a direction-determiningalgorithm, a velocity-determining algorithm, or an algorithm combininglocation, direction, and/or velocity determination to determine whethertag 1104 is passing through exit 1120. In some embodiments, the LPS mayuse one or more of the techniques described in international applicationserial number PCT/US14/26319 filed on Mar. 13, 2014 and herebyincorporated by reference in its entirety. For example, the LPS may usetwo or more exit beams 1130 to track the movement (if any) of tag 1104based on a multi-session, non-acknowledging inventorying procedure asdescribed in the above-referenced international application.

The LPS may also (or instead) determine the location of tag 1104 toconfirm whether tag 1104 is inside or outside facility 1102, for exampleusing one or more techniques described above or in internationalapplication serial number PCT/US14/26319 as referenced previously. Inone example, the LPS may determine the location of tag 1104 based onwhere an RF signal from tag 1104 emanates from or originates. If the LPSdetermines that an RF signal from tag 1104 emanates from within facility1102, the LPS may determine that tag 1104 is within facility 1102. Ifthe LPS determines that an RF signal from tag 1104 emanates from outsidefacility 1102, the LPS may determine that tag 1104 is outside facility1102. The LPS may determine the location from which an RF signalemanates using angle-of-arrival (described below), the identity ororientation of beams in which the RF signal was received, and/or anyother suitable parameter indicative of RF signal emanation location. TheLPS may determine that tag 1104 and its associated item are exitingfacility 1102 if it determines that tag 1104 is inside facility 1102 butmoving towards exit 1120 or if tag 1104 is near or passing through exit1120. In some embodiments, if the LPS determines that tag 1104 isoutside facility 1102, the LPS may determine that tag 1104 and itsassociated item has exited facility 1102 even if the LPS did not detecttag 1104 passing through an entrance or exit of facility 1102.

After determining tag read parameters as described above, the LPS maystore the tag read parameter(s) in a database (e.g., database 1160) forfuture reference. For example, upon determining a tag read parameterassociated with tag 1104, the LPS may associate the tag read parameterwith an identifier of tag 1104 in database 1160. Subsequently, upondetecting a tag reply, the LPS may use the stored tag read parameters toassist in identifying the replying tag and/or determining somecharacteristic of the replying tag (e.g., whether the replying tag hasmoved, whether the tag is in an appropriate location, whether the taghas been authorized to exit facility 1102, or any other suitablecharacteristic).

A third action that the LPS may perform is determining whether tag 1104and its associated item are authorized to exit facility 1102. In someembodiments the LPS may determine whether a tag is authorized to exitfacility 1102 based on one or more of the techniques described in U.S.Pat. Nos. 8,593,257, 8,866,595, 8,872,636, 8,866,596, and 9,189,904, allof which are hereby incorporated by reference in their entireties. Forexample, the LPS may read (via reader 1110 or another reader) data suchas an electronic signature, a ticket, and/or an exit code or sold codefrom tag 1104, and may use the data to determine whether tag 1104 andits associated item are authorized to leave facility 1102, inconjunction with database 1160 which may contain information aboutwhether tags are authorized to exit facility 1102) or independently. Insome embodiments, the LPS may determine whether tag 1104 is authorizedto leave facility 1102 by determining whether tag 1104 is on a list oftags and associated items authorized to leave facility 1102.

As a result of the various actions described above, the LPS candetermine whether tag 1104 and its associated item belong to facility1102, are exiting facility 1102, and are authorized to do so. If soauthorized then the LPS permits tag 1104 and its associated item to exitfacility 1102 (in other words, allows tag 1104 and its associated itemto exit without taking security actions as described below), and mayrecord information about the exit (e.g., time of exit, location of exit,tag and item exiting, other tags or items exiting at the same time,etc.) in the memory of reader 1110 or other readers, in database 1160,or in any other suitable local or remote memory.

On the other hand, if the LPS determines that tag 1104 is not authorizedto exit facility 1102 then it may take one or more security actionsusing implemented security features. For example, security actions mayinclude issuing alerts, monitoring the unauthorized exit, attempting toprevent the unauthorized exit, and/or any other suitable action forpreventing or hindering the exit of tag 1104 through exit 1120. In someembodiments, the LPS may issue alerts by activating an audible, silent,or visual alarm, activating a security system, activating a securityprocedure, alerting an entity associated with facility 1102 (e.g., anemployee or manager), notifying an authority (e.g., security personnel,police personnel, military personnel, a facility supervisor, or anyother authorized person), writing an alert code to the tag 1104 (e.g., acode that notifies a reader reading tag 1104 that tag 1104 or itsassociated item has been stolen), refraining from writing a code to tag1104 (e.g., refraining from writing a code indicating that tag 1104 isauthorized to exit), adjusting a record associated with the tag 1104and/or its associated item (for example, in the memory of reader 1110 orother readers, in database 1160, or in some other memory) to indicatethe unauthorized exit, and/or sending a message regarding theunauthorized exit to an entity or authority associated with facility1102 or to some external entity or authority (e.g., a local policedepartment). The LPS may monitor the unauthorized exit by directing acamera toward exit 1120 and/or taking a picture or a video from a cameradirected toward exit 1120. The LPS may attempt to prevent theunauthorized exit by securing a physical barrier such as by locking adoor or gate or activating an obstruction (e.g., a barrier) associatedwith exit 1120.

In some embodiments reader 1110 may be used both for loss-prevention andfor inventorying tags or items in facility 1102, for example forstock-keeping purposes. For example, reader 1110 may be positioned togenerate exit beams 1130 and at least one internal beam 1140 directedwithin facility 1102. As shown in FIG. 11, internal beam 1140 may bedirected to a display 1170 holding items with tagged merchandise. Inother embodiments, internal beams may be directed to shelves,containers, pallets, racks, counters, cases, boxes, portions of theabove, or any other suitable tag or item organization means. Reader 1110may use internal beam 1140 to identify, locate, track, and/orauthenticate tagged items within facility 1102. Upon reading a taggeditem associated with facility 1102, reader 1110 may update a server ordatabase (e.g., database 1160) with information about the tagged item,such as its location and/or movement.

As described above, the LPS may be configured to determine whether a tagis stationary or moving. In some embodiments, the LPS may be configuredto respond differently based on whether a tag is stationary or inmotion. For example, in situations where facility 1102 contains a largenumber of tagged items, the LPS may be configured to suppress reads ofstationary tags, thereby allowing it to devote more time to readingmoving tags or other tags of interest. In some embodiments, the LPS maycause a stationary tag not to participate in one or more subsequentinventory rounds using the refresh or multi-session non-acknowledgingfunctionalities described in international application serial numberPCT/US14/26319 referenced above.

In some embodiments, the LPS may be configured to increase the rate atwhich moving tags are inventoried, and may be configured to maintain orreduce the rate at which stationary tags are inventoried. For example,the LPS may determine whether a tag is in motion based on beam readcounts, angle-of-arrival measurements, or any other suitable method. Insome embodiments, a tag in motion may notify the LPS of its movement,for example via a tag reply or by asserting a stored flag. If the LPSdetermines that an inventoried tag is in motion, it may increase therate at which the tag is inventoried or participates in inventoryrounds, for example by transmitting inventory commands specificallytargeting the tag, successively inventorying the tag withoutinventorying other tags, increasing the tag inventorying rates of thebeams at or near the tag's location, using a non-acknowledgingfunctionality as described herein, or using any other suitabletechniques. If the LPS instead determines that an inventoried tag isstationary, it may either maintain or reduce the rate at which the tagis inventoried, for example by suppressing tag reads using the refreshfunctionality described above.

In some embodiments, an LPS may determine where a tag is located and/orwhether the tag is moving based on angle-of-arrival informationassociated with RF waves or signals from the tag. FIG. 12 depicts howthe angle-of-arrival of an RF wave can be determined. Diagram 1200depicts a situation in which two receivers 1204 and 1206 detect an RFwave from an RFID tag 1202. Receivers 1204 and 1206 may be separatereaders, or separate antennas or antenna elements coupled to a singlereader or to multiple readers, and may be configured to each transmitdifferent beams or together synthesize a single beam oriented in aparticular direction, as described above. Receivers 1204 and 1206 andtag 1202 may be disposed such that distance r₁ between tag 1202 andreceiver 1204 is greater than distance r₂ between tag 1202 and receiver1206. Accordingly, an RF wave or signal originating from tag 1202 willfirst arrive at receiver 1206 and then arrive at receiver 1204, assumingthat the propagation paths between tag 1202 and the receivers 1204 and1206 are relatively equivalent except for distance.

The difference between the RF wave as seen at receiver 1204 and the RFwave as seen at receiver 1206 may be characterized as a time differenceor a phase difference. The former may be determined by comparing thetime at which a particular wavefront of the RF wave arrives at receiver1204 to the time at which the same wavefront arrives at receiver 1206.The latter may be determined by comparing the phases of the RF wavesobserved at receiver 1204 and receiver 1206 at a particular time.

For example, consider RF wave 1210. At some initial time, tag 1202begins to transmit or backscatter RF wave 1210. Receiver 1206 observesthe beginning of RF wave 1210 before receiver 1204, because receiver1206 is closer to tag 1202 than receiver 1204. At some later time T,receiver 1204 then observes the beginning of RF wave 1210 as wavefront1212. At the same time T, receiver 1206 observes wavefront 1214, whichis a portion of RF wave 1210 subsequent to the wavefront 1212. Thedifference between wavefront 1212 and wavefront 1214 may be representedas a phase difference 1232, as depicted in diagram 1230. Phasedifference 1232, when combined with the (known) distance d betweenreceiver 1204 and receiver 1206, may be used to determine the angle θbetween axis 1220 on which receivers 1204 and 1206 lie and a line thatintersects both tag 1202 and the point on axis 1220 midway betweenreceivers 1204 and 1206. This angle θ may be referred to as the“angle-of-arrival” (or AoA) of RF wave 1210 with respect to thereceivers 1204 and 1206, and represents the angle from which RF wave1210 arrived, and therefore may represent the angle at which tag 1202 islocated with respect to the receivers 1204 and 1206.

Instead of or in addition to using RF wave phase offsets, in someembodiments edge offsets in an RF signal or symbol offsets in a tagreply may be used to determine AoA. In some embodiments, a reply sent bytag 1202 may encode a particular symbol sequence at a particular tagsymbol rate, for example as described in the Gen2 Specification. Thepropagation distance difference between tag 1202 and receivers 1204 and1206 may cause receiver 1204 to receive particular symbol(s) slightlyafter receiver 1206 receives the same symbol(s). The timing differencein the reception of the symbol(s) may then be used to determine the AoAof the tag reply and tag 1202.

Before determining the AoA of a received tag reply, the controllercoupled to receivers 1204 and 1206 may first determine whether the tagreplies or RF waves received at receivers 1204 and 1206 are in factversions of the same signal that are phase-shifted with respect to eachother. For example, a controller may determine whether the signalsreceived at receivers 1204 and 1206 are modulated in the same way,encode the same symbols at the same tag symbol rate, or otherwiseoriginate from the same source. The controller may also determinewhether the signals received at receivers 1204 and 1206 are offset orphase-shifted with respect to each other. For example, the controllermay determine whether the two signals have a phase offset. In someembodiments, the controller may buffer at least a portion of aninitially-received tag signal and compare the buffered portion to aportion of a subsequently-received tag signal, using an appropriatephase or symbol offset if necessary. If the two portions substantiallymatch, then the controller may conclude that the initially-received andsubsequently-received tag signals correspond to the same tag signal. Ifthe controller also determines that the two signals have a phase offset,then the controller may conclude that the two signals are phase-shiftedwith respect to each other.

Using a tag signal's AoA measured with respect to a single axis (e.g.,axis 1220) localizes the tag's location to a conical surface (or acircular area if the angle-of-arrival is) 90° defined by the AoA and theaxis. Further physical constraints may further localize the taglocation. For example, receivers 1204 and 1206 may be mounted on aceiling or wall and configured to look downward or outward, which maylocalize the tag location to at most half of the conical surface definedby the AoA. Furthermore, if receivers 1204 and 1206 are mounted on aceiling and facing a floor, then the tag location may be furtherlocalized to be within some distance of the floor (or equivalently atleast some distance away from the ceiling).

In some embodiments, additional AoA measurements made using otherreceivers may also be used to localize a tag. Diagram 1260 depicts threenon-collinear receivers 1264, 1266, and 1268. The receivers are disposedsuch that receivers 1264 and 1266 lie on axis 1270, receivers 1266 and1268 lie on axis 1272, and receivers 1264 and 1268 lie on axis 1274, butreceivers 1264, 1266, and 1268 do not share a single axis. When a replyfrom tag 1262 is received, receivers 1264 and 1266 may be used todetermine a first AoA θ₁ of the reply with respect to axis 1270,receivers 1266 and 1268 may be used to determine a second AoA θ₂ of thereply with respect to axis 1272, and receivers 1264 and 1268 may be usedto determine a third AoA θ₃ of the reply with respect to axis 1274. Oncetwo or more reply AoAs measured with respect to different axes areknown, triangulation may be used to further localize the location of tag1262. Using AoA measurements from three or more receivers, in additionto providing two-dimensional location capability as described above, mayallow tag location to be further refined. For example, AoA measurementsof a tag taken from three or more receivers that are not necessarilycollinear may allow the direction and/or the distance of the tag withrespect to the receivers to be determined with more accuracy, forexample by using a linear fit or some other fitting algorithm.

FIG. 13 depicts several examples of how angle-of-arrival may be used todetermine the location, direction, and/or velocity of a moving tag.Diagram 1300 depicts a facility 1302, similar to facility 1102, with anSBR 1312 positioned to monitor facility exit 1304. SBR 1312 has multipleantenna elements, and may be configured to perform AoA measurements withits antenna elements as described in FIG. 12 to determine tag location.Initially, SBR 1312 may detect a reply from tag 1306 within facility1302 with an AoA 1322. Subsequently, SBR 1312 may detect another replyfrom tag 1306 with a different AoA 1324. SBR 1312 (or an LPS coupled toSBR 1312) may be able to use the AoAs 1322 and 1324 to determine atravel parameter associated with tag 1306. For example, as describedabove SBR 1312 may be able to determine the location of tag 1306 at aparticular time based on the measured AoAs 1322 and 1324. SBR 1312 mayalso be able to determine whether tag 1306 is stationary or moving. IfAoAs 1322 and 1324 had been substantially similar, SBR 1312 may concludethat tag 1306 is substantially stationary. On the other hand, if AoAs1322 and 1324 are substantially different, as depicted in diagram 1300,SBR 1312 may conclude that tag 1306 is moving. SBR 1312 may further beable to conclude based from the AoAs 1322 and 1324 that tag 1306 has atravel direction toward exit 1304. If timestamps associated with AoAs1322 and 1324 are available, SBR 1312 may also be able to determine anaverage travel velocity of tag 1306 in the time duration between themeasurements of AoAs 1322 and 1324.

Diagram 1330 depicts facility 1332, similar to facility 1302, with areader 1342 positioned to monitor facility exit 1334. Reader 1342 maynot be an SBR, but is configured with multiple antenna elements for AoAdetermination. Similar to the situation described in diagram 1300,reader 1332 may initially detect a reply from tag 1336 with an AoA 1352,and may subsequently detect another reply from tag 1336 with a differentAoA 1354. Reader 1332 (or an LPS or controller coupled to reader 1332)may then use the AoAs 1352 and 1354, as well as associated timestamps,to determine one or more travel parameters associated with tag 1336,such as its location, whether it is stationary or traveling, and if thelatter its direction of travel and/or velocity of travel.

Diagram 1362 depicts facility 1362, similar to facilities 1332 and 1302,with two readers 1372 and 1374 positioned to monitor facility exit 1364.Readers 1372 and 1374 are configured with multiple antenna elements forAoA determination and are depicted as similar to reader 1342, but inother embodiments, one or both of readers 1372/1374 may be SBRs similarto SBR 1312. Readers 1372 and 1374 may initially detect a reply from tag1366, with reader 1372 measuring AoA 1382 and reader 1374 measuring AoA1386. Subsequently, readers 1372 and 1374 may detect another reply fromtag 1366, with reader 1372 measuring AoA 1384 and reader 1374 measuringAoA 1388. Readers 1372 and 1374 (or an LPS/controller coupled to bothreaders) may then use the AoAs 1382-1388, as well as associatedtimestamps, to determine one or more travel parameter(s) associated withtag 1366, as described above. In some embodiments, the additional AoAmeasurements from the additional reader may be used to further refinethe travel parameter determination process.

In some embodiments, read zones may be used for tag inventorying ortracking purposes. A read zone may be based on the field-of-view orcoverage volume of one or more readers or antennas, and may correspondexactly to a reader/antenna coverage volume, may include portions ofmultiple coverage volumes, or may correspond to part of a coveragevolume. In some embodiments, read zones may correspond to particularregions in a facility. For example, different rooms, corridors,entrances, and exits in a building may be different read zones. Asanother example, individual fixtures, such as shelving units, individualshelves, cabinets, or tables may be different read zones. In someembodiments, different parts of an individual fixture (e.g., differentsections of a shelf) may be different read zones. Different read zonesmay at least partially intersect, or may be entirely disjoint. In someembodiments, a read zone may entirely contain one or more other readzones.

FIG. 14 depicts how RFID readers may be configured to provide read zonesin an environment, according to embodiments. Diagram 1400 depicts thecoverage area of SBR 1402, similar to coverage area 1080 of SBR 1010. Insome embodiments, SBR 1402 may be configured to provide a number of readzones, each corresponding to an individual SBR beam or combination ofSBR beams. For example, beam 1408 of SBR 1402 may correspond to a firstread zone, and beams 1404 and 1406 may together correspond to a secondread zone. If SBR 1402 reads a tag using beam 1408, it may conclude thatthe tag resides in the first read zone. If instead SBR 1402 reads a tagusing beam 1404 or beam 1406, it may conclude that the tag resides inthe second read zone.

Diagram 1430 depicts coverage area 1434 of flood reader 1432. A floodreader, unlike an SBR, may be configured to generate a single,relatively static beam. In some embodiments, coverage area 1434 may bedivided into multiple read zones. For example, coverage area 1434 may bedivided into at least an inner zone 1436 and a periphery zone 1438. Insome embodiments, flood reader 1432 may be configured to determinewhether a detected tag is in inner zone 1436 or periphery zone 1438 bydetermining the AoA (described above) associated with a response fromthe tag. Accordingly, flood reader 1432 may be configured with two ormore antenna elements. The antenna elements may be arranged such thatflood reader 1432 can determine the AoA of a received tag response andthereby determine whether the responding tag resides in inner zone 1436or periphery zone 1438. Of course, in other embodiments other techniquesmay be used to determine whether a detected tag is in inner zone 1436 orperiphery zone 1438. For example, the flood reader 1432 may use areceived signal strength indicator (RSSI) to determine where a detectedtag resides, or may use one or more of the location-determiningtechniques described above.

Diagram 1460 depicts how individual read zones may be provided bymultiple read points. Diagram 1460 depicts space 1462, which may be partor all of a facility such as facility 1102, described above. A number ofRFID read points (which may include readers and/or reader antennas)1464-1474 may be deployed to provide coverage of at least a portion ofspace 1462, if not substantially the entire space 1462. Read points1464-1474 may be part of an LPS as described above, in which read points1464-1474 cooperate with each other and/or are coordinated by a centralcontroller, or may be configured to operate independently. In someembodiments, the operation mode of each read point may be dynamic. Forexample, a particular read point may switch between independentoperation, cooperating operation, and central-controller-drivenoperation based on time, environmental conditions, or any other suitableparameter.

Space 1462 may include one or more read zones, as described above. Forexample, space 1462 may include read zone 1480, read zone 1482, and readzone 1484. Read zones 1480-1484 may correspond to particular regions ofspace 1462, specific fixtures within space 1462, and/or differentportions of fixtures within space 1462, and may not exactly coincidewith read point coverage volumes. For example, read zone 1480 includesportions (but not all of) of the coverage volumes of read points 1464and 1468, read zone 1484 includes portions of the coverage volumes ofread points 1472 and 1474, and read zone 1482 includes portions of thecoverage volumes of read points 1464-1470. In such situations, the LPSmay determine whether an inventoried tag is within a read zone by firstdetermining the location of an inventoried tag (e.g., via AoA and/orother techniques described herein) and then determining whether the taglocation is within any read zones. In some embodiments, the LPS maystore or have access to information about the size, location, and/orboundaries of read zones 1480-1484, for example in the form of physicalcoordinates with respect to one or more fixed reference points or theidentity of marker or infrastructure tags associated with specific readzones and read zone boundaries. Upon detecting a tag, the LPS maydetermine one or more location parameters associated with the tag, suchas AoA parameters, distance parameters, physical coordinates, and thelike. The LPS may then compare the determined location parameters toread zone information to determine whether the detected tag is withinone or more read zones.

In some embodiments, the LPS may be configured to adjust inventoryingparameters based on whether a detected tag is located in a particularread zone or not. For example, the LPS may be configured to inventory atag at a higher rate if the LPS determines that the tag is located in aread zone associated with relatively high tag or item movement.Conversely, the LPS may be configured to inventory a tag at a lower rateif the tag is located in a read zone associated with relatively low tagor item movement. In some embodiments, such inventorying parameteradjustment may be used for loss-prevention purposes, as described below.

FIG. 15 depicts how RFID readers may be used to monitor tagged items atparticular risk of theft, according to embodiments. Diagram 1500 depictsa space 1502 with RFID tags 1510 and 1512. Space 1502 may be a facilitythat stores RFID-tagged items, such as a warehouse or a retailestablishment. Space 1502 further includes read point 1522, positionedto monitor and inventory tags and tagged items within space 1502. Readpoint 1522 may be a reader such as a flood reader or an SBR, or anantenna coupled to a reader, and may be part of a larger LPS or mayoperate independently. Read point 1522 may be configured to communicatewith database 1520, which may store information about tags, items,and/or read zones within space 1502, similar to database 1160 describedabove.

Space 1502 further includes an entrance or exit 1504, through whichcustomers and/or employees may enter or exit space 1502, near or at aboundary of space 1502. A read zone 1506 may be defined near exit 1504for loss-prevention purposes. For example, tagged items within read zone1506 and therefore relatively close to the exit 1504 and the associatedboundary of space 1502 may have a higher probability or risk ofinappropriately leaving (for example, as a result of being stolen) space1502 than tagged items within space 1502 but not within read zone 1506,due to item proximity to the exit 1504. The probability or risk that atagged item inappropriately leaves, exits, or transitions from space1502 is referred to as the tagged item's “transition risk”, and may becorrelated to the probability of theft of the tagged item. Read point1522 may be configured to have read zone 1506 within its coveragevolume. For example, read point 1522 may be configured to associatecertain locations, AoA ranges, and RF beams (if an SBR or otherwiseconfigured to generate and/or manage multiple RF beams) with read zone1506. Read point 1522 may be further configured to determine whether adetected tag is located within read zone 1506 and is associated with anitem that has a relatively high transition risk. In response todetermining that a particular tag is associated with an item having arelatively high transition risk, read point 1522 may adjust one or moreinventorying parameters to increase the probability or likelihood thatan inappropriate (e.g., unauthorized) transition of the tag from space1502 is detected.

For example, tags 1510 and 1512, each associated with a respectivetagged item, are present in space 1502. Tag 1510 is positionedrelatively near exit 1504 and within read zone 1506, whereas tag 1512 ispositioned relatively far from exit 1504, outside of read zone 1506 andpotentially in one or more other read zones (not depicted). During taginventorying, read point 1522 may detect and locate tags 1510 and 1512.Read point 1522 may further determine that tag 1510 is located withinread zone 1506 (for example, because a reply from tag 1510 is receivedon a beam oriented at read zone 1506) and therefore its associated itemmay have a relatively high transition risk, while tag 1512 is notlocated within read zone 1506 (for example, because replies from tag1512 were not received on a beam oriented at read zone 1506) andtherefore its associated item may have a relatively low transition risk.In response, read point 1522 may adjust one or more inventoryingparameters associated with tag 1510 and/or read zone 1506 to increasethe probability that an inappropriate transition of items associatedwith tag 1510 and/or other tags within read zone 1506 is detected. Forexample, read point 1522 may cause tag 1510 to respond more frequentlyto inventory commands, as described below. As another example, if readpoint 1522 is an SBR, it may increase the rate at which it switches tothe beams oriented toward read zone 1506 with respect to beams orientedelsewhere, or it may increase the duration of beams oriented toward readzone 1506 with respect to beams oriented elsewhere. The increased rateor duration of beams oriented toward read zone 1506 with respect tobeams oriented elsewhere may allow tags within zone 1506 to be detectedand inventoried more frequently than tags located elsewhere, therebyincreasing the probability that an inappropriate transition of a taggeditem within zone 1506 is detected. In some embodiments, read point 1522may also have the option of adjusting inventorying parameter(s)associated with tag 1512 upon determining that tag 1512 is associatedwith an item having a relatively low transition risk. For example, readpoint 1522 may not adjust any inventorying parameters associated withtag 1512. As another example, read point 1522, if an SBR, may reduce therate at which it switches to the beam(s) oriented toward tag 1512 and/ormay reduce the duration of beams oriented toward tag 1512.

In some embodiments, read point 1522 may use a nonacknowledgementprocess, as described in international application serial numberPCT/US14/26319 referenced above, to inventory tag 1510 or other tagsassociated with items having relatively high transition risk. A taginventorying process (for example, as described in the Gen2Specification) involves a series of inventory rounds, where eachinventory round includes a number of steps in which information isexchanged between a reader and one or more tags. Reader-tag exchanges inindividual inventory rounds may cause state changes in the participatingreader and/or tags—for example, the reader may request an identifierfrom a tag, the tag may reply with its identifier, the reader mayacknowledge receipt of the identifier, and the tag may then assert asession flag associated with a specific session (e.g, S0, S1, S2, or S3according to the Gen2 Specification) in response to the acknowledgement,thereby switching from a first state (in which a particular session flagis unasserted) to a second state (in which the particular session flagis asserted). The tag in the second state may not participate in atleast one subsequent inventory round for the specific session byrefraining from responding to reader inventory commands targeting tagswith unasserted session flags for the specific session (i.e., tags inthe first state). This increases the probability that other,uninventoried tags are inventoried by the reader, but also in effectreduces the rate at which the tag is read by the reader. If an itemassociated with the tag has a relatively high transition risk (e.g., asa result of being positioned near an exit or being of relatively highvalue), then there may be a corresponding increase in the probabilitythat an inappropriate transition of the tagged item will go undetected.

In some embodiments, a reader may perform a nonacknowledgement processto prevent the tag from asserting its session flag for a particularsession, thereby preventing the tag from switching to the second state.The reader may perform the nonacknowledgement process by beginning aninventory round as described above, but either (a) not acknowledgereceipt of the tag-provided identifier or (b) transmit anonacknowledgement command to the tag. The NAK command in the Gen2Specification is one such nonacknowledgement command, although othercommands in the Gen2 Specification may have the effect of anonacknowledgement command (i.e., prevent the tag from asserting aparticular session flag or entering the second state). Performing thenonacknowledgement process for a particular tag and a particular sessionmay avoid a reduction in detection rate of the tag and the correspondingincrease in undetected transition probability, because the tag remainsin the first state and will continue to participate in subsequentinventory rounds for that particular session. However, thenonacknowledgement process also potentially reduces the probability thatother, uninventoried tags are inventoried by the reader, because thealready-inventoried tag can still participate in subsequent inventoryrounds for that particular session and potentially prevent uninventoriedtags from responding to the reader. Accordingly, the reader may beconfigured to use the nonacknowledgement process only for tagsassociated with items that have relatively high transition risks.

Timing diagram 1550 depicts a nonacknowledgement process that may beused for tags with differing transition risks. Timing diagram 1550displays the values of S1 flags for tags 1510 and 1512. While S1 flagsare used in the following description, in other embodiments other flags(e.g., S0, S2, S3, Select) may be used. In timing diagram 1550, a flagis asserted when its value is high and not asserted when its value islow. The horizontal axis of timing diagram 1550 represents time, withevents to the left preceding events to the right.

At initial time 1560, a reader (e.g., read point 1522) may begin a firstinventory round (e.g., as described in the Gen2 Specification) byinventorying tags in the first state (i.e., with unasserted S1 flags).For example, the reader may first transmit a query-type command (e.g.,as described in the Gen2 Specification) specifying tags with unassertedS1 flags, then continue inventorying the selected tags serially. Thereader may be configured to determine the location of a tag whileinventorying the tag, for example using AoA or any other suitablelocation technique. According to timing diagram 1550, both tags 1510 and1512 are in the first state and have S1 flags that are not asserted, andwill participate in the first inventory round. Suppose that the readerfirst begins to inventory tag 1512. During the inventorying process, thereader may determine that tag 1512 is not located within read zone 1506or is located within a different read zone. Accordingly, the reader maydetermine that the item associated with tag 1512 has a relatively lowprobability or risk of inappropriate transition from space 1502, and maycomplete the inventorying process by causing tag 1512 to assert its S1flag and switch to the second state.

The reader may then begin to inventory tag 1510. During the inventoryingprocess, the reader may determine that tag 1510 is located within readzone 1506. Accordingly, the reader may determine that the itemassociated with tag 1510 has a relatively high probability or risk ofinappropriate transition from space 1502, and may modify theinventorying process to prevent tag 1510 from asserting its S1 flag andentering the second state. The reader may modify the inventoryingprocess by not responding to a reply from tag 1510, transmitting anonacknowledgement command (e.g., a NAK command according to the Gen2Specification) to tag 1510, or transmitting another command that eitherprevents tag 1510 from asserting its S1 flag or causes tag 150 todeassert its S1 flag, thereby preventing tag 1510 from switching to thesecond state.

At time 1562, the reader may perform a second inventory round in whichit again attempts to inventory tags in the first state. Tag 1512, havingbeen inventoried at time 1560, is in the second state, and thereforewill not respond to reader inventory commands targeting tags in thefirst state and will not participate in the second inventory round. Tag1510, on the other hand, is still in the first state due to readermodification of the inventorying process at time 1560, and may thereforerespond to reader inventory commands targeting tags in the first stateand participate in the second inventory round, resulting in an effectiveincrease in detection rate for tag 1510 as compared to tag 1512. As attime 1560, during the inventorying process at time 1562 the reader mayagain determine that the item associated with tag 1510 has a relativelyhigh probability or risk of inappropriate transition from space 1502,and accordingly may again modify the inventorying process, preventingtag 1510 from asserting its S1 flag and switching to the second state.

Subsequently, at time 1564, the reader may perform a third inventoryround in which it again inventories tags in the first state. At somepoint between time 1562 and 1564, the S1 flag of tag 1512 may decay toan unasserted state, causing tag 1512 to switch to the first state. As aresult, at time 1564 both tags 1510 and 1512 may respond to readerinventory commands targeting tags in the first state and participate inthe third inventory round. Similar to time 1560, the reader maydetermine that the item associated with tag 1512 has a relatively lowprobability of inappropriate transition, whereas the item associatedwith tag 1510 has a relatively high probability of unauthorizedtransition. Accordingly, the reader may cause tag 1512 to switch to thesecond state and prevent tag 1510 from switching to the second state.

In some embodiments, the reader may use an alternate nonacknowledgementprocess in which all tags are first inventoried beforehigh-transition-risk tags are separated out. In this process, the readerfirst inventories all visible (or selected) tags and switches them tothe second state. Subsequently, the reader identifies the inventoriedtags that have relatively high transition risk and switch those tagsback to the first state. The reader then maintains thehigh-transition-risk tags in the first state using thenonacknowledgement process described herein. The alternatenonacknowledgement process may allow the reader more time to identifyhigh-transition-risk tags, because the reader has to inventory all thetags first, and can therefore determine whether an inventoried tag has ahigh transition risk without being constrained by protocol timingrequirements.

While transition risk is described above in terms of read zones, otherparameters may also (or instead) be used to determine transition risk,such as tag distance to exit (determined using AoA, beam identifier, orother location determination techniques), item physical size (smalleritems may have relatively higher transition risks and larger items mayhave relatively lower transition risks), sensitivity (sensitive items,such as dangerous items or items associated with confidentialinformation, may have relatively higher transition risks), value(valuable or expensive items may have relatively higher transitionrisks), motion (moving tags may have relatively higher transitionrisks), or any other suitable parameter.

FIG. 16 is a flowchart of an item-monitoring process 1600 according toembodiments. Process 1600 begins at step 1602, where a reader (e.g., areader in an LPS) begins to inventory a particular tag. At step 1604,the reader evaluates the transition risk of an item associated with thetag, based on tag location, tag identity, tag environment, and/or anyother suitable parameter. For example, the reader may determine whetherthe tag is located in a read zone that is near an exit, entrance, orpotential transition point. If so, the reader may determine that theitem associated with the tag has a relatively high transition risk. Asanother example, the reader may determine the item associated with thetag is sensitive, has a small physical size, and/or has relatively highvalue, as described above. If so, the reader may determine that the itemassociated with the tag has a relatively high transition risk. As yetanother example, the reader may determine whether the tag is in motion.If so, the reader may determine that the item associated with the taghas a relatively high transition risk. In some embodiments, the readermay be configured to derive a quantitative transition risk measurementand compare the measurement to a predefined or dynamic threshold todetermine whether the item associated with the tag has a relatively hightransition risk.

If the reader determines at step 1604 that the item associated with thetag does not have a relatively high transition risk, at step 1606 thereader may complete the tag inventorying process and cause the tag toassert an associated session flag. For example, the reader may cause thetag to assert a session flag and switch to a second state. On the otherhand, if the reader determines at step 1604 that the item associatedwith the tag does have a relatively high transition risk, at step 1608the reader may modify the tag inventorying process as described above inFIG. 15 in order to continue detecting the tag at a relatively highrate. For example, the reader may transmit a nonacknowledgement command,may ignore a response from the tag, or may begin the inventoryingprocess anew.

FIG. 17 is a flowchart of a loss-prevention process 1700 according toembodiments. Process 1700 begins at step 1702, where a facility checkoutstation (e.g., checkout station 1150) reads an identifier from a tagassociated with a tagged item. The identifier may be a tag identifier oran item identifier. At step 1704, the checkout station authorizes thetagged item to leave the facility in response to receiving and verifyingauthorizing information, as described above. The checkout stationupdates a local or remote database (e.g., database 1160) at step 1706 toindicate that the tagged item is authorized to leave the facility, andmay also (or instead) writing data to the tag indicating that it isauthorized to leave the facility.

Subsequently, at step 1708 one or more readers scan for tagged itemsexiting the facility using one or more beams directed at or nearfacility exits. The reader(s) may scan for tagged items using exit beams(for example, as described in FIG. 11), by determining angles-of-arrivalassociated with tag replies (for example, as described in FIGS. 12-13),and/or by determining tag presence in read zones (for example, asdescribed in FIGS. 14-15). In some embodiments, the reader(s) maydetermine that a tag is departing the facility based on its location,its direction-of-travel, and/or its velocity-of-travel. For example, ifthe reader(s) determines, using exit beam identifiers, read zoneidentifiers, and/or measured AoAs, that a tag is outside the facility,then it may determine that the tag has departed the facility, especiallyif the tag is otherwise associated with the facility as described below.As another example, the reader(s) may determine that a tag with adirection-of-travel or velocity-of-travel oriented into or within thefacility is not departing and accordingly ignore the tag forexit-tracking purposes, but determine that a tag with adirection-of-travel or velocity-of-travel oriented out of the facilityis departing the facility. The reader(s) may scan for tagged itemsexiting the facility while inventorying tagged items within thefacility, as described above.

Upon detecting a tagged item departing the facility (e.g., based on thedirection-of-travel, velocity-of-travel, and/or location of the tagassociated with the item, as described above), in step 1710 the LPSdetermines whether the tagged item is authorized to exit the facility.The LPS may retrieve an identifier from the tag associated with the itemand compare the identifier to a database or a derived identifier, asdescribed above. In some embodiments, the LPS may also (or instead)retrieve an electronic signature, ticket, and/or exit code or sold codefrom the tag for use in determining whether the tagged item isauthorized to leave the facility. In some embodiments, the LPS may firstdetermine whether the item is associated with the facility. For example,the LPS may determine whether the tag identifier is included in afacility database, or whether an owner code read from the tag isassociated with the facility. If not, the LPS may ignore the tag and itsassociated item. If the LPS determines that the item is associated withthe facility and authorized to leave the facility then the LPS permitsthe item to exit at step 1712. If the LPS determines that the item isassociated with the facility but not authorized to leave then at step1714 the LPS may perform or initiate a security action. For example, theLPS may issue alert(s), monitor the unauthorized exit, and/or attempt toprevent the unauthorized exit, as described above.

The steps described in processes 1600 and 1700 are for illustrationpurposes only. Loss prevention may be performed employing additional orfewer steps and in different orders using the principles describedherein. The order of the steps may be modified, some steps eliminated,or other steps added according to other embodiments.

As described above, the RF beams for transmitting and/or receiving maybe synthesized by an SBR or generated without the use of asynthesized-beam antenna. For example, a transmit beams may be generatedby a synthesized-beam antenna but the receive beam may employ a staticantenna such a patch, monopole, dipole, etc. As another example, thesynthesized beams may be replaced by multiple static antennas coupled toone or more readers.

According to some examples, a method for monitoring RFID-tagged items ina facility is provided. The method may include transmitting a firstinventory command configured to cause tags in a first state toparticipate in a first inventory round and receiving a first reply froma first tag in the first inventory round. The method may further includedetermining that a first item associated with the first tag has a lowtransition risk based on the first reply and causing the first tag toswitch to a second state based on the low transition risk. The methodmay further include receiving a second reply from a second tag in thefirst inventory round, determining that a second item associated withthe second tag has a high transition risk based on the second reply, andcausing the second tag to remain in the first state based on the hightransition risk. The method may further include transmitting a secondinventory command configured to cause tags in the first state toparticipate in a second inventory round, receiving a third reply fromthe second tag in the second inventory round, determining that thesecond item has inappropriately exited the facility based on the thirdreply, and issuing an alert.

According to some embodiments, the method may include determining anitem's transition risk based on a physical size and/or a value of theitem. Determining that the first item has the low transition risk mayinclude determining that the first item is located within a first zoneand/or receiving the first reply on a first beam. Determining that thesecond item has the high transition risk may include determining thatthe second item is located within a second zone different from the firstzone, determining that the second item is close to an entrance or anexit of the facility, and/or receiving the second reply on a second beamdifferent from the first beam. Determining that the second item hasinappropriately exited the facility may include determining that an RFsignal of the third reply emanates from outside the facility.

According to other embodiments, causing the second tag to remain in thefirst state may include transmitting a nonacknowledgement command or nottransmitting an acknowledgement command to the second tag. Determiningthat the second item has inappropriately exited from the facility mayinclude determining that the second item is not on a list of itemauthorized to leave the facility and/or determining that the second tagdoes not contain a code indicating that the second item is authorized toleave the facility. Issuing the alert may include activating an alarm,notifying an authority, adjusting a record associated with the seconditem, and/or writing an alert code to the second tag.

According to other examples, a method for a synthesized-beamradio-frequency identification reader (SBR) to monitor RFID-tagged itemsin a facility is provided. The method may include synthesizing a firstbeam directed substantially into the facility, transmitting a firstinventory command on the first beam that is configured to cause tags ina first state to participate in a first inventory round, and receiving afirst reply from a first tag in the first inventory round. The methodmay further include determining that a first item associated with thefirst tag has a low transition risk based on the first reply and causingthe first tag to switch to a second state based on the low transitionrisk. The method may further include receiving a second reply from asecond tag in the first inventory round, determining that a second itemassociated with the second tag has a high transition risk based on thesecond reply, and causing the second tag to remain in the first statebased on the high transition risk. The method may further includesynthesizing a second beam directed substantially outside the facilityand transmitting a second inventory command on the second beamconfigured to cause tags in the first state to participate in a secondinventory round. The method may further include receiving a third replyfrom the second tag in the second inventory round, determining that thesecond item has inappropriately exited the facility based on the thirdreply, and issuing an alert.

According to some embodiments, determining that the first item has thelow transition risk may include determining that a first RF signal ofthe first reply has a first angle-of-arrival, determining that the firstitem is located within a first zone, and/or receiving the first reply ona first beam. Determining that the second item has the high transitionrisk may include determining that a second RF signal of the second replyhas a second angle-of-arrival different from the first angle-of-arrival,determining that the second item is located within a second zonedifferent from the first zone, determining that the second item is inproximity to an entrance or an exit of the facility, and/or receivingthe second reply on a second beam different from the first beam.

According to other embodiments, the SBR system may include multipleSBRs. The method may include determining an item's transition risk basedon a physical size and/or a value of the item. Causing the second tag toremain in the first state may include transmitting a nonacknowledgementcommand or not transmitting an acknowledgement command to the secondtag. Determining that the second item has inappropriately exited fromthe facility may include determining that the second item is not on alist of item authorized to leave the facility and/or determining thatthe second tag does not contain a code indicating that the second itemis authorized to leave the facility. Issuing the alert may includeactivating an alarm, notifying an authority, adjusting a recordassociated with the second item, and/or writing an alert code to thesecond tag.

According to further examples, a method for a radio-frequencyidentification (RFID) reader system including multiple antennas tomonitor RFID-tagged items in a facility is provided. The method mayinclude directing a first beam substantially into the facility from afirst antenna, transmitting a first inventory command on the first beamthat is configured to cause tags in a first state to participate in afirst inventory round, and receiving a first reply from a first tag inthe first inventory round. The method may further include determiningthat a first item associated with the first tag has a low transitionrisk based on the first reply and causing the first tag to switch to asecond state based on the low transition risk. The method may furtherinclude receiving a second reply from a second tag in the firstinventory round, determining that a second item associated with thesecond tag has a high transition risk based on the second reply, andcausing the second tag to remain in the first state based on the hightransition risk. The method may further include directing a second beamsubstantially outside the facility from a second antenna andtransmitting a second inventory command on the second beam configured tocause tags in the first state to participate in a second inventoryround. The method may further include receiving a third reply from thesecond tag in the second inventory round, determining that the seconditem has inappropriately exited the facility based on the third reply,and issuing an alert.

According to some embodiments, the reader system may include multiplereaders. The method may further include determining an item's transitionrisk based on a physical size of the item, a value of the item, a zonewithin which the item is located, and/or a proximity of the item to anentrance and/or an exit of the facility. Causing the second tag toremain in the first state may include transmitting a nonacknowledgementcommand or not transmitting an acknowledgement command. Determining thatthe second item has inappropriately exited from the facility may includedetermining that the second item is not on a list of item authorized toleave the facility and/or determining that the second tag does notcontain a code indicating that the second item is authorized to leavethe facility. Issuing the alert may include activating an alarm,notifying an authority, adjusting a record associated with the seconditem, and/or writing an alert code to the second tag.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes via the use of block diagrams and/orexamples. Insofar as such block diagrams and/or examples contain one ormore functions and/or aspects, it will be understood by those within theart that each function and/or aspect within such block diagrams orexamples may be implemented individually and/or collectively, by a widerange of hardware, software, firmware, or virtually any combinationthereof. Those skilled in the art will recognize that some aspects ofthe embodiments disclosed herein, in whole or in part, may beequivalently implemented employing integrated circuits, as one or morecomputer programs running on one or more computers (e.g., as one or moreprograms running on one or more computer systems), as one or moreprograms running on one or more processors (e.g. as one or more programsrunning on one or more microprocessors), as firmware, or as virtuallyany combination thereof, and that designing the circuitry and/or writingthe code for the software and/or firmware would be well within the skillof one of skill in the art in light of this disclosure.

The present disclosure is not to be limited in terms of the particularembodiments described in this application, which are intended asillustrations of various aspects. Many modifications and variations canbe made without departing from its spirit and scope, as will be apparentto those skilled in the art. Functionally equivalent methods andapparatuses within the scope of the disclosure, in addition to thoseenumerated herein, will be apparent to those skilled in the art from theforegoing descriptions. Such modifications and variations are intendedto fall within the scope of the appended claims. The present disclosureis to be limited only by the terms of the appended claims, along withthe full scope of equivalents to which such claims are entitled. It isto be understood that this disclosure is not limited to particularmethods, configurations, antennas, transmission lines, and the like,which can, of course, vary. It is also to be understood that theterminology used herein is for the purpose of describing particularembodiments only, and is not intended to be limiting.

With respect to the use of substantially any plural and/or singularterms herein, those having skill in the art can translate from theplural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations may be expressly set forth herein for sakeof clarity.

It will be understood by those within the art that, in general, termsused herein, and especially in the appended claims (e.g., bodies of theappended claims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.). It will be further understood by those within the art that if aspecific number of an introduced claim recitation is intended, such anintent will be explicitly recited in the claim, and in the absence ofsuch recitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to embodiments containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should be interpreted to mean “at least one”or “one or more”); the same holds true for the use of definite articlesused to introduce claim recitations. In addition, even if a specificnumber of an introduced claim recitation is explicitly recited, thoseskilled in the art will recognize that such recitation should beinterpreted to mean at least the recited number (e.g., the barerecitation of “two recitations,” without other modifiers, means at leasttwo recitations, or two or more recitations).

Furthermore, in those instances where a convention analogous to “atleast one of A, B, and C, etc.” is used, in general such a constructionis intended in the sense one having skill in the art would understandthe convention (e.g., “a system having at least one of A, B, and C”would include but not be limited to systems that have A alone, B alone,C alone, A and B together, A and C together, B and C together, and/or A,B, and C together, etc.). It will be further understood by those withinthe art that virtually any disjunctive word and/or phrase presenting twoor more alternative terms, whether in the description, claims, ordrawings, should be understood to contemplate the possibilities ofincluding one of the terms, either of the terms, or both terms. Forexample, the phrase “A or B” will be understood to include thepossibilities of “A” or “B” or “A and B.”

As will be understood by one skilled in the art, for any and allpurposes, such as in terms of providing a written description, allranges disclosed herein also encompass any and all possible subrangesand combinations of subranges thereof. Any listed range can be easilyrecognized as sufficiently describing and enabling the same range beingbroken down into at least equal halves, thirds, quarters, fifths,tenths, etc. As a non-limiting example, each range discussed herein canbe readily broken down into a lower third, middle third and upper third,etc. As will also be understood by one skilled in the art all languagesuch as “up to,” “at least,” “greater than,” “less than,” and the likeinclude the number recited and refer to ranges which can be subsequentlybroken down into subranges as discussed above. Finally, as will beunderstood by one skilled in the art, a range includes each individualmember. Thus, for example, a group having 1-3 cells refers to groupshaving 1, 2, or 3 cells. Similarly, a group having 1-5 cells refers togroups having 1, 2, 3, 4, or 5 cells, and so forth.

We claim:
 1. A Radio Frequency Identification (RFID) componentcomprising: an interface configured to receive replies from RFID tags;and a processor block coupled to the interface and configured to:receive, via the interface, a reply from a tag participating in aninventory round; determine, based on at least the received reply,whether an item associated with the tag is moving; and if the item isdetermined to be moving, then cause the tag to be inventoried at a firstinventory rate, else cause the tag to be inventoried at a secondinventory rate different from the first inventory rate.
 2. The RFIDcomponent of claim 1, wherein the processor block is configured todetermine whether the item is moving based on at least a firstangle-of-arrival of the received reply and a second angle-of-arrival ofanother received reply.
 3. The RFID component of claim 1, wherein theprocessor block is configured to determine whether the item is movingbased on one or more of a tag read count or a tag read rate.
 4. The RFIDcomponent of claim 1, wherein the processor block is configured todetermine whether the item is moving based on an indication from the tagin the received reply.
 5. The RFID component of claim 1, wherein thecomponent is one of integrated in an RFID reader and configured to becoupled to the RFID reader.
 6. The RFID component of claim 5, wherein:the first inventory rate is higher than the second inventory rate; andthe processor block is configured to cause the tag to be inventoried atthe first inventory rate by one of: causing the RFID reader to transmita nonacknowledgement command, and causing the RFID reader to refrainfrom transmitting an acknowledgement command.
 7. The RFID component ofclaim 1, wherein the processor block is configured to cause the tag tobe inventoried at the first inventory rate by adjusting one or more of:the frequency at which an RFID reader system uses beams oriented towarda location of the tag for inventorying, or a duration of beams orientedtoward the tag location.
 8. A Radio Frequency Identification (RFID)component comprising: an interface configured to receive replies fromRFID tags; and a processor block coupled to the interface and configuredto: receive, via the interface, a reply from a tag participating in aninventory round; determine, based on at least the received reply,whether an item associated with the tag is moving; and cause an RFIDreader to adjust whether the tag participates in a subsequent inventoryround based on whether the item is determined to be moving.
 9. The RFIDcomponent of claim 8, wherein the processor block is further configuredto cause the RFID reader to: cause the tag to participate in thesubsequent inventory round if the item is determined to be moving, andcause the tag to refrain from participating in the subsequent inventoryround if the item is determined not to be moving.
 10. The RFID componentof claim 8, wherein the processor block is configured to determinewhether the item is moving based on at least a first angle-of-arrival ofthe received reply and a second angle-of-arrival of another receivedreply.
 11. The RFID component of claim 8, wherein the processor block isconfigured to determine whether the item is moving based on one or moreof a tag read count or a tag read rate.
 12. The RFID component of claim8, wherein the processor block is configured to determine whether theitem is moving based on an indication from the tag in the receivedreply.
 13. The RFID component of claim 8, wherein the component is oneof integrated in the RFID reader and configured to be coupled to theRFID reader.
 14. The RFID component of claim 8, wherein the processorblock is further configured to cause the RFID reader to adjust one ormore of: the frequency at which the RFID reader uses beams orientedtoward a location of the tag for inventorying, or a duration of beamsoriented toward the tag location.
 15. A method for monitoring anRFID-tagged item, the method comprising: receiving, from an RFID readersystem, a reply from a tag participating in an inventory round;determining, based on at least the received reply, whether an itemassociated with the tag is moving; and if the item is determined to bemoving, then causing the RFID reader system to inventory the tag at afirst inventory rate, else causing the RFID reader to inventory the tagat a second inventory rate different from the first inventory rate. 16.The method of claim 15, further comprising determining whether the itemis moving based on at least a first angle-of-arrival of the receivedreply and a second angle-of-arrival of another received reply.
 17. Themethod of claim 15, further comprising determining whether the item ismoving based on one or more of a tag read count or a tag read rate. 18.The method of claim 15, further comprising determining whether the itemis moving based on an indication from the tag in the received reply. 19.The method of claim 15, wherein the first inventory rate is higher thanthe second inventory rate and the method further comprises causing theRFID reader system to inventory the tag at the first inventory rate byone of: causing the RFID reader system to transmit a nonacknowledgementcommand, and causing the RFID reader system to refrain from transmittingan acknowledgement command.
 20. The method of claim 15, furthercomprising causing the RFID reader system to inventory the tag at thefirst inventory rate by adjusting one or more of: the frequency at whichthe RFID reader system uses beams oriented toward a location of the tagfor inventorying, or a duration of beams oriented toward the taglocation.